- dovecot - dovecot.org

[Dovecot] Autocreation of sieve filters
by Angel L. Mateo 14 Nov '13

14 Nov '13

Hello, Is there any way to create a predefined sieve filters during mailbox autocreation? What I want is that my user's mailboxes are automatically created (using mailbox option in namespaces) but I want them to have a predefined sieve script. Using a postlogin script could be an idea, but I'd prefer an automatic one, because postlogin only will filter after first user login -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 868888337

2 3

[Dovecot] trashed
by Nick Edwards 14 Nov '13

14 Nov '13

On 11/12/13, Reindl Harald <h.reindl(a)thelounge.net> wrote: > tell that Noel which is blocking my messages and so did > not read what i quoted from Benny's trolling but opens > his mouth > > tell that Noel which is abusing his power by set complete > IP-ranges on RBL lists he maintains because he does not > like one person using a mailserver on that range besides > many other people > Let us see Posfix list - BANNED Roundcube List - MODERATED Centos List - MODERATED (maybe banned) Fedora list - 1/ MODERATED - 2/ Had hissy fit temper tantrum with moderators a few days ago about his continual moderation and claimed was quitting fedora list. Likely has resubscribed to Fedora (if indeed even did quit), like on Postfix under a lists(a)rhsoft.net address or something similar and thats only the ones *I* know about. So, your in a blacklist as well? wouldnt have anything to do with your actions pretty much everywhere would it now, nooooooooooooooooooooooooooooo, of course not. Taking into account all of the above, I think its fair to say, its more than one person that doesn't like your foul mouthed antics, which was explained to you many times by fedora moderators, trying to get you to change, all you had to do, and they would remove moderation, but you refused, so you deserve it, no one else to blame but yourself YOU ARE NOT THE VICTIM >>> blocked using >>> bl.alt-backspace.org; This range is used by caustic Internet troll >>> Harald >>> Reindl h.reindl(a)thelounge.net / ACCESS DENIED - see >>> http://www.alt-backspace.org/usage.php#misc (in reply to RCPT TO >>> command) Awesome! Thanks for that, I have just enabled bl.alt-backspace.org on our company servers ciao

6 11

Re: [Dovecot] Dovecot login slow
by Joseph Tam 14 Nov '13

14 Nov '13

> ssl_ca = </usr/share/ssl/certs/rapidssl.crt > ssl_cert = </usr/share/ssl/certs/imapd.pem > ssl_key = </usr/share/ssl/certs/imapd.pem > > These lines look weird to me. Why do they have a < ? Red herring; this is standard. I think it means "feed this file into stdin". On 11/13/2013 12:41 PM, Marc Perkel wrote: >>> Takes about 10 seconds and it lets me in. I'm using MYSQL and it's a >>> small indexed database on a fast server so it's not the mysql query that's >>> slowing it down. At least I don't think it is. But - kind of stumped. Just >>> wondering if there's something obvious I'm overlooking. I think maybe turning up the verbosity on logging will help. If that doesn't, try process tracing the dovecot auth process. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Dovecot 2.0.9 Quota Limit issues
by David Johnson 14 Nov '13

14 Nov '13

Hello, I've tried searching for information regarding this problem but haven't found anything. Currently I have a Dovecot 2.0.9 with virtual users from a SQL table. Right now I'm only using global quota limits. Here is my quota setup: plugin { quota = maildir:User quota quota_rule = *:storage=3G quota_rule2 = Trash:storage=+100M quota_rule3 = Archive:storage=+1G quota_rule4 = Archive/2013:storage=+1G quota_rule5 = Junk:ignore } According to the documentation this should allow the Archive folder to have an additional 1G in it that is not counted toward the global 3G. However I have users who have 2G in the Archive folder, and about 1G elsewhere. At this point they stop receiving emails due to quota exceeded. doveadm quota get -u <user> displays this: Quota name Type Value Limit % User quota STORAGE 3150312 3145728 100 User quota MESSAGE 8271 - 0 If I change Archive:storage=+1G to Archive:ignore then they can receive emails again. After the change doveadm quota get -u displays this: Quota name Type Value Limit % User quota STORAGE 1266885 3145728 40 User quota MESSAGE 8271 - 0 Is there something I'm missing as to why this setup isn't working? Thanks! -- David J.

2 2

[Dovecot] Can't see e-mails
by Muzaffer Tolga Ozses 12 Nov '13

12 Nov '13

Hi, I have a postfix+dovecot+mysql+roundcube setup. I recently changed providers. At the moment, postfix can receive e-mails but either dovecot or roundcube can't see e-mails. I did a telnet example.com 143 then a login user pass and this is what I see: 2013-11-12 16:08:51 auth: Debug: sql(alanya(a)boradental.com.tr,193.255.135.254): SELE CT '/var/vmail/boradental.com.tr/alanya' as home, 'maildir:/var/vmail/ boradental.com .tr/alanya' as mail, 5000 AS uid, 5000 AS gid, concat('dirsize:storage=', quota) AS quota FROM mailbox WHERE username = 'alanya(a)boradental.com.tr' AND active = '1' 2013-11-12 16:08:51 auth: Debug: master out: USER 3767009281 alanya@borad ental.com.tr home=/var/vmail/boradental.com.tr/alanya mail=maildir:/va r/vmail/boradental.com.tr/alanya uid=5000 gid=5000 quota=dirsize:storage=0 so I'm assuming dovecot works. Am I right to assume this? If I'm not, what's the solution? If I am, how can I debug this? Regards,

2 2

[Dovecot] how to make quota per user ??
by ihab 12 Nov '13

12 Nov '13

I use dovecot version 1.2.15 and i put quota for all users , now i want to give more size for some emails , i already added the quota to user database , and i added the queries from http://wiki.dovecot.org/Quota/1.1 MySQL: user_query = select uid, gid, home, \ concat('*:bytes=', quota_bytes) as quota_rule \ from users where userid = '%u' # MySQL with userdb prefetch: Remember to prefix quota_rule with userdb_ # (just like all other userdb extra fields): password_query = select userid as user, password, \ uid as userdb_uid, gid as userdb_gid, \ concat('*:bytes=', quota_bytes) as userdb_quota_rule \ from users where userid = '%u' but it is not work what i have to change and in which files please ? -- View this message in context: http://dovecot.2317879.n4.nabble.com/how-to-make-quota-per-user-tp45335.html Sent from the Dovecot mailing list archive at Nabble.com.

3 2

[Dovecot] my quota warning script not getting executed2
by ihab 12 Nov '13

12 Nov '13

Why is my quota warning script not getting executed? :( dovecot version is 1.2.15 this is part of dovecot.conf protocol imap { listen = 127.0.0.1:143 #ji1 quota config mail_plugins = quota } quota = maildir:User quota quota_rule = *:storage=2M quota_exceeded_message=Quota exceeded please go http://www.go.com . quota_warning = storage=99%% /usr/local/bin/quota-warning.sh 99 %u quota_warning2 = storage=98%% /usr/local/bin/quota-warning.sh 98 %u quota_warning3 = storage=97%% /usr/local/bin/quota-warning.sh 97 %u and this is quota-warning.sh FROM="postmasterEmail" msg="From: $FROM To: TEST EMAIL Subject: Your email quota is 10% full Your mailbox is now 10% full." echo -e "$msg" | /usr/sbin/sendmail -f $FROM "TEST EMAIL " exit 0 -- View this message in context: http://dovecot.2317879.n4.nabble.com/my-quota-warning-script-not-getting-ex… Sent from the Dovecot mailing list archive at Nabble.com.

3 3

[Dovecot] Dovecot MTA
by Timo Sirainen 12 Nov '13

12 Nov '13

Hi all, I've never really wanted to create my own MTA, because I like Postfix quite a lot. And I always thought it would require a horribly lot of time to be able to create something that was anywhere even close to having Postfix's features. (I would shudder to even think about recreating Dovecot from scratch nowadays.) But slowly over time I've also been thinking of ways how things could be done a bit better, and I think I have enough ideas to start thinking about Dovecot MTA more seriously in a few more months (after my current busy schedule calms down a bit). And (unlike Dovecot!) I'm not planning on taking over the world with the MTA (or at least not very quickly), but it would definitely be useful for many installations I know of. My main design goals for the MTA are: * In normal load don't queue mails, just continue delivering the mail through different processes/services until it succeeds or fails, and only after that return ok/failure to the SMTP client. So there's no (forced) post-queue filtering, everything would normally happen pre-queue. This is required because in Germany (and EU in general?) you aren't allowed to just drop spams after SMTP server has responsed OK to the client, even if you’re 100% sure it’s a spam. So this would also mean that the SMTP DATA replies will come more slowly, which means that the SMTP server must be able to handle a lot more concurrent SMTP connections, which means that in large installations the smtpd process must be able to asynchronously handle multiple SMTP client connections. * In some cases you can't really avoid placing mails into a queue. This could be because of temporary failures or maybe because of an abnormal load spike. A mail queue in local disk isn't very nice though, because if the local disk dies, the queued mails are lost. Dovecot MTA will allow the queue to be in object storage and it will also likely support replication (similar to current dsync replication). In both of these cases if a server dies, another server can quickly take over its queue and continue handling it. * Dovecot MTA is a new product, which means we can add some requirements to how it's being used, especially related to securely sending emails between servers. It could do a bunch of checks at startup and fail to even start if everything isn't correct. Here are some things I had in mind - not sure if all of these are good ideas or not: - Require DKIM configuration. All outgoing mails will be DKIM signed. - Require the domain’s DNS to contain _submission._tcp SRV record (and actually might as well require _imap._tcp too) - Require SSL certificates to be configured and always allow remote to use STARTTLS - Require DANE TLSA record to exist and match the server's configured SSL cert - Have very good (and strict?) DNSSEC support. If we know a remote server is supposed to have valid DNSSEC entries, but doesn't, fail to deliver mail entirely? - Add a new DNS record that advertises this is a Dovecot MTA (or compatible). If such entry is found (especially when correctness is guaranteed by DNSSEC), the email sender can assume that certain features exist and work correctly. If they don't, it could indicate an attack and the mail sending should be retried later. This DNS record would of course be good to try to standardize. * Configuration: It would take years to implement all of the settings that Postfix has, but I think it's not going to be necessary. In fact I think the number of new settings to dovecot.conf that Dovecot MTA requires would be very minimal. Instead nearly all of the configuration could be done using Sieve scripts. We'd need to implement some new MTA-specific Sieve extensions and a few core features/configurations/databases that the scripts can use, but after that there wouldn't be really any limits to what could be done with them. * Try to implement as many existing interfaces as possible (e.g. Milter and various Postfix APIs like policy servers) so that it wouldn’t be necessary to reimplement all the tools and filters. So perhaps something like this could be done in time for Dovecot v2.4. Any thoughts/ideas/suggestions?

30 76

[Dovecot] blames for using maillists ?
by Benny Pedersen 12 Nov '13

12 Nov '13

why do you not simply shut up? # sieve rule require ["imap4flags"]; # rule:[reindl] if allof (header :contains "From" "h.reindl(a)thelounge.net") { setflag ["\\Seen","\\Flagged"]; stop; }

3 3

[Dovecot] dsync-server panic/fatal errors
by IT geek 31 11 Nov '13

11 Nov '13

Would anyone like to hazard a guess what these errors mean: Nov 11 18:57:04 server2 dovecot: dsync-server(mark): Panic: file mbox-lock.c: line 799 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) Nov 11 18:57:04 server2 dovecot: dsync-server(mark): Fatal: master: service(doveadm): child 3119 killed with signal 6 (core not dumped - set service doveadm { drop_priv_before_exec=yes }) Getting this replication working is driving me nuts! :'-( Any help would be appreciated. -Mark

1 0

[Dovecot] Incorrect Responses on deliverable mails with LMTP server
by Thomas Leuxner 11 Nov '13

11 Nov '13

Appears some change between 2.2.6 and 2.2.7 altered the response codes for LMTP user verification probes. Dovecot 2.2.6: Nov 2 15:50:48 spectre postfix/qmgr[627]: 3dBjr80wMgz1s: from=<double-bounce(a)spectre.leuxner.net>, size=271, nrcpt=1 (queue active) Nov 2 15:50:48 spectre postfix/cleanup[6226]: 3dBjr80xbYz1w: message-id=<20131102145047.2D3C6824147(a)sam.dfn-cert.de> Nov 2 15:50:48 spectre postfix/lmtp[6228]: 3dBjr80wMgz1s: to=<tlx(a)leuxner.net>, orig_to=<security(a)leuxner.net>, relay=spectre.leuxner.net[private/dovecot-lmtp], delay=0.03, delays=0/0.01/0.01/0.01, dsn=2.1.5, status=deliverable (250 2.1.5 OK) Dovecot 2.2.7: Nov 5 05:24:04 spectre postfix/qmgr[627]: 3dDHnc5J06z1s: from=<double-bounce(a)spectre.leuxner.net>, size=271, nrcpt=1 (queue active) Nov 5 05:24:04 spectre postfix/smtpd[2484]: 3dDHnc5KWcz1w: client=web.heise.de[193.99.144.71] Nov 5 05:24:04 spectre postfix/cleanup[2489]: 3dDHnc5KWcz1w: message-id=<E1VdXxN-0002Gx-0s.01(a)web.heise.de> Nov 5 05:24:04 spectre postfix/lmtp[2491]: 3dDHnc5J06z1s: to=<tlx(a)leuxner.net>, orig_to=<newsletters(a)leuxner.net>, relay=spectre.leuxner.net[private/dovecot-lmtp], delay=0.03, delays=0/0.01/0.01/0, dsn=4.4.2, status=undeliverable (lost connection with spectre.leuxner.net[private/dovecot-lmtp] while sending MAIL FROM) While it still seems to work, mail gets delivered, it looks pretty ugly in the logs. Regards Thomas

2 2

[Dovecot] server side private/public key
by Peter Mogensen 11 Nov '13

11 Nov '13

*Christian Felsing wrote: * > Please consider to add server side private/public key encryption for incoming mails. > If client logs on, the password is used to unlock users server side private key. > If mail arrives from MTA or any other source, mail is encrypted with users public key. > Key pair should be located in LDAP or SQL server. PGP and S/MIME should be supported. > This is for the situation if NSA or other organizations asks admin for > users mail insistently, So ... exactly which security threat are you thinking about preventing here? This won't protect against: * NSA listening in on the mails when they arrive. * NSA taking a backup of your mails and wait for your first attempt to read them - at which time they'll have your private key in plain text. It seems like a much wider protection to just keep you private key for your self. /Peter

3 2

[Dovecot] Can't get sieve/managedsieve working
by Alter Depp 11 Nov '13

11 Nov '13

Hi, I am running dovecot 2.1.7 for a while, with roundcube webmail frontend 0.9.5 . Now I wanted to add sieve to filter mails. Unfortunately most tutorials are for dovecot 1.x but I'm running dovecot 2 on debian wheezy. I could upload some scripst with sieve-connect, checked and activated them. When I try to edit filters with thunderbird sieve plugin 0.2.2 nothing happens. If I try to edit filters with roundcube managesieve plugin nothing happens, too, but I get some errors in logfile: > roundcube: "Authentication failed." (3) > roundcube: Not currently in AUTHORISATION stata (1): Can someone help me, to get it running? # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.6.11+ armv6l Debian 7.2 auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = plain lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = * mail_location = mbox:~/mail:INBOX=/var/mail/%u 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 ihave namespace { inbox = yes location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { special_use = \Trash name = Trash } prefix = name = inbox } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = stefan@localhost protocols = " imap sieve" service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service { inet_listener { port = 4190 name = sieve } name = managesieve-login } service login/sieve { name = managesieve } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </etc/ssl/certs/ssl-cert-raspi.pem ssl_key = </etc/ssl/certs/ssl-cert-raspi.pem userdb { driver = passwd } protocol lmtp { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { mail_plugins = " sieve" service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol sieve { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } }

5 7

[Dovecot] maildir_very_dirty_syncs and GFS
by Andrea gabellini - SC 11 Nov '13

11 Nov '13

Hello, I have two dovecot 2.2.7 and postfix with LDA backend that shares a GFS partition as email storage. In front of them there is a proxy with Director. In both backend servers only Dovecot access the cur/ directory. Can I use maildir_very_dirty_syncs=yes? Thanks, Andrea -- ---------------------------------------------------------------- That is what learning is. You suddenly understand something you've understood all your life, but in a new way. ---------------------------------------------------------------- Ing. *Andrea Gabellini* Email: andrea.gabellini(a)telecomitalia.sm <mailto:Andrea%20Gabellini%20%3Candrea.gabellini@telecomitalia.sm%3E> Skype: andreagabellini Tel: (+378) 0549 886111 Fax: (+378) 0549 886188 Telecom Italia San Marino S.p.A. Strada degli Angariari, 3 47891 Rovereta Republic of San Marino http://www.telecomitalia.sm

1 0

Re: [Dovecot] Dovecot MTA
by Peter Mogensen 11 Nov '13

11 Nov '13

Timo Sirainen wrote: > And Dovecot roadmap is slowly shrinking .. there aren’t all that many > big features left anymore. Soon it’s mainly going to be improvements > to reliability and performance. So I need to find some new things to > do in any case. :) True ... If I try to make a wish list for features many of them requires fixing the IMAP protocol it self. (Like not having the folder display name being the unique identifier) Which reminds me that the IMAP5 process (if there ever was one) seems to be slowed to a halt. Now, there's a task for a developer looking for something to do ;-) /Peter

1 0

[Dovecot] Getting debug output from antispam plugin with dspam
by Igor Zinovik 11 Nov '13

11 Nov '13

Hello. I'm trying to get some output from antispam plugin when it invokes dspam binary for retraining. Currently I see no messages related to dspam execution. Dovecot IMAP server works as 'vmail' user: # ps aux|grep 'dovecot/imap' vmail 3062 0.7 0.0 29824 3008 ? S 16:22 0:00 dovecot/imap User 'vmail' is listed as trusted in /etc/dspam/dspam.conf # fgrep vmail /etc/dspam/dspam.conf Trust vmail Dovecot IMAP plugins and antispam configuration: # doveconf -n | egrep -e '(^#|antispam|protocol imap)' # 2.2.7: /etc/dovecot/dovecot.conf # OS: Linux 3.7.10-1.16-default x86_64 openSUSE 12.3 (x86_64) antispam_allow_append_to_spam = YES antispam_backend = dspam antispam_dspam_args = --client;--user;%Lu;--deliver=spam,innocent;--source=error;--signature=%%s antispam_dspam_binary = /usr/sbin/dspam antispam_dspam_notspam = --class=innocent antispam_dspam_result_header = X-DSPAM-Result antispam_dspam_spam = --class=spam antispam_signature = X-DSPAM-Signature antispam_signature_missing = move antispam_spam = Spam antispam_trash = trash;Trash;Deleted;deleted;Deleted Items protocol imap { mail_plugins = expire mail_log notify quota trash imap_quota antispam Antispam plugin is successfully loaded: # grep antispam_plugin /var/log/dovecot/dovecot.log Nov 11 16:22:32 imap: Debug: Module loaded: /usr/lib64/dovecot/modules/lib90_antispam_plugin.so As i understand plugin would not work with message that do not contains dspam signature, so I sent GTUBE message to myself and when I move it to Spam folder I see only Dovecot messages: Nov 11 16:28:06 imap(zinovik(a)example.org): Info: copy from INBOX: box=Spam, uid=3422, msgid=<20131111144014.731f035b871deb0e082bc22e(a)example.org>, size=1130 Nov 11 16:28:06 imap(zinovik(a)example.org): Info: delete: box=INBOX, uid=26792, msgid=<20131111144014.731f035b871deb0e082bc22e(a)example.org>, size=1130 Nov 11 16:28:06 imap(zinovik(a)example.org): Info: expunge: box=INBOX, uid=26792, msgid=<20131111144014.731f035b871deb0e082bc22e(a)example.org>, size=1130 Dspam logs nothing, though debugging is turned on # ps aux | egrep -e '^dspam' dspam 2939 0.0 0.0 116408 2420 ? S 15:38 0:00 /usr/sbin/dspam --daemon --debug # egrep '^Debug ' /etc/dspam/dspam.conf Debug * Even if I set dspam binary to file that do not exist i do not get any debugging messages (according to code function i_debug("execution %s failed...") should be triggered). Maybe there is some kind of verbose output knob for plugins in Dovecot? I turned on everything I found (also using mail_log for imap protocol): # doveconf -n|egrep -e '(verbose|debug)' auth_debug = yes auth_verbose = yes mail_debug = yes verbose_ssl = yes Is there anybody out there who use Dovecot 2.2.7 with antispam plugin? Antispam plugin revision 5ebc6aae4d7c<http://hg.dovecot.org/dovecot-antispam-plugin/rev/5ebc6aae4d7c>

1 0

[Dovecot] Dovecot replication not redirecting if server is down
by Patrick Westenberg 11 Nov '13

11 Nov '13

Hi everyone, I'm running a test environment with a proxy in front of working replication between two backends but redirecting in case of a backend failure is not working. Nov 09 21:03:59 imap-login: Error: proxy(mail(a)example.net): connect(10.5.29.211, 143) failed: Connection refused (after 0 secs, local=10.5.29.201:38333) I appreciate any advice. Regards Patrick Proxy: # 2.2.7: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes default_process_limit = 150 director_mail_servers = 10.5.29.211 10.5.29.212 director_servers = 10.5.29.201 director_user_expire = 5 mins disable_plaintext_auth = no lmtp_proxy = yes log_path = /var/log/dovecot.log mail_plugins = notify replication 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 ihave passdb { args = proxy=y nopassword=y driver = static } protocols = imap pop3 lmtp sieve service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener auth-userdb { user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 10.5.29.201 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director } service lmtp { inet_listener lmtp { address = 10.5.29.201 port = 24 } } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } } service pop3-login { executable = pop3-login director } service replicator { unix_listener replicator-doveadm { mode = 0600 } } ssl = no protocol lmtp { auth_socket_path = director-userdb } Backend 1: # 2.2.7: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no dotlock_use_excl = no doveadm_password = secret doveadm_port = 12345 dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u hostname = mb01.example.net listen = 10.5.29.211 log_path = /var/log/dovecot.log mail_debug = yes mail_fsync = always mail_gid = vmail mail_home = /var/mail/%d/%n mail_location = maildir:~/Maildir mail_plugins = quota notify replication mail_uid = vmail 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 ihave mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spamverdacht { auto = subscribe } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:10.5.29.212 quota = dict:User quota::file:%h/Maildir/dovecot-quota quota_rule2 = INBOX.Trash:ignore quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_after = /usr/local/etc/dovecot/sieve/sieve_after.sieve sieve_default = /usr/local/etc/dovecot/sieve/default.sieve sieve_dir = ~/sieve } postmaster_address = postmaster(a)example.net protocols = imap pop3 lmtp sieve service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener auth-userdb { mode = 0666 user = vmail } } service doveadm { inet_listener { port = 12345 } } service lmtp { inet_listener lmtp { address = 10.5.29.211 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /usr/local/etc/dovecot/quota_warning.sh unix_listener quota-warning { user = vmail } user = root } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl = no submission_host = mf01.example.net userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota notify replication sieve } protocol imap { mail_max_userip_connections = 30 mail_plugins = quota notify replication imap_quota } Backend 2: # 2.2.7: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no dotlock_use_excl = no doveadm_password = secret doveadm_port = 12345 dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u hostname = mb02.example.net listen = 10.5.29.212 log_path = /var/log/dovecot.log mail_debug = yes mail_fsync = always mail_gid = vmail mail_home = /var/mail/%d/%n mail_location = maildir:~/Maildir mail_plugins = quota notify replication mail_uid = vmail 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 ihave mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spamverdacht { auto = subscribe } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:10.5.29.211 quota = dict:User quota::file:%h/Maildir/dovecot-quota quota_rule2 = INBOX.Trash:ignore quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_after = /usr/local/etc/dovecot/sieve/sieve_after.sieve sieve_default = /usr/local/etc/dovecot/sieve/default.sieve sieve_dir = ~/sieve } postmaster_address = postmaster(a)example.net protocols = imap pop3 lmtp sieve service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener auth-userdb { mode = 0666 user = vmail } } service doveadm { inet_listener { port = 12345 } } service lmtp { inet_listener lmtp { address = 10.5.29.212 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /usr/local/etc/dovecot/quota_warning.sh unix_listener quota-warning { user = vmail } user = root } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = no submission_host = mf01.example.net userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota notify replication sieve } protocol imap { mail_max_userip_connections = 30 mail_plugins = quota notify replication imap_quota }

6 10

[Dovecot] sieve + notify + $subject$ + empty subject = segv
by Christian Ferbar 11 Nov '13

11 Nov '13

Hello, we can reproduce a bug where lmtp crashes: LMTP telnet session: Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. 220 lisa.m-otion.at Dovecot ready. lhlo xyz 250-xyz.m-otion.at 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING mail from:<xyz(a)m-otion.at> 250 2.1.0 OK rcpt to:<my_mailbox> 250 2.1.5 OK data 354 OK From:<xyz(a)m-otion.at> test . Connection closed by foreign host. /var/log/messages tells me: Nov 11 00:07:00 mail kernel: lmtp[15868]: segfault at 0000000000000000 rip 00002b1960d01d70 rsp 00007fff3fa95908 error 4 pigeonhole 0.4.2, dovecot 2.2.6 and this is what I found out: If you use a sieve script containing the following line notify :method "mailto" :options "xyz" :message "$from$*#+$subject$"; and send a mail without a Subject: header line lmtp crashes. The bug is related to the sieve module in /src/lib-sieve/plugins/notify/ext-notify-common.c:266. The line contains only a check if mail_get_headers_utf8 returns an error. So the workaround for this line would be to add a check if header[0] is not NULL. if ( (mail_get_headers_utf8(msgdata->mail, "subject", &header) >= 0) && header[0] ) str_append(out_msg, header[0]); IMHO this patch should be applied to the "$from$" replacement as well. The comments in the dovecot's header file says for mail_get_headers: Returns -1 if error, 0 otherwise (with or without headers found). hope it helps, Regards Christian Ferbar

2 1

[Dovecot] Replication on v2.2.6 - I'm stuck (again)
by IT geek 31 10 Nov '13

10 Nov '13

Hi, I'm trying to get Dovecot replication working between two servers. I didn't have much luck on v2.1.3, so after receiving advice from the list I have upgraded to v2.2.6. I now get the error: Oct 30 11:50:16 server1 dovecot: doveadm(mark): Error: user mark: Auth PASS lookup failed Oct 30 11:50:16 server2 dovecot: doveadm(mark): Error: sync: /var/run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because doveadm_port is set) Here is my config: # 2.2.6: /usr/pkg/etc/dovecot/dovecot.conf # OS: NetBSD 5.2 cobalt auth_mechanisms = plain login doveadm_password = mylittlesecret doveadm_port = 12345 dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u listen = 192.168.1.1 login_greeting = Go on then, let's have it... mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = " notify replication" passdb { driver = passwd } plugin { mail_replica = remote:vmail@server2.mydomain.com replication_full_sync_interval = 1 hours } protocols = imap service aggregator { fifo_listener replication-notify-fifo { mode = 0600 user = vmail } unix_listener replication-notify { mode = 0600 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service doveadm { inet_listener { port = 12345 } } service imap-login { inet_listener imap { port = 0 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl_cert = </etc/openssl/certs/mail.mydomain.com.crt ssl_key = </etc/openssl/private/mail.mydomain.com.key userdb { driver = passwd } protocol lda { postmaster_address = postmaster(a)mydomain.com Can anyone give me some guidance on where I've gone wrong with my config? Any help would be appreciated, -Mark

2 7

[Dovecot] Question about folder sharing
by Achim Gottinger 09 Nov '13

09 Nov '13

Hi, I run dovecot (2.1.7) on debian wheezy in conjuniction with postfix, samba4 (as ldap backend) and sogo. I configured folder sharing but have an few issues. With my current config users can share the inbox and other folders. If the acl allows creatings subfolders this does work for all folders beside inbox. What i want to archiev is the following: If an user shares his inbox, others should be able to create subfolders and those should inherit the inboxe's acl. All subfolders of inbox should appear as folders at root level and not as subfolders of the inbox. I thought this can be done by setting the prefix of namespace inbox to INBOX/. I did this and changed the IMAP Server Folder setting in thunderbird to INBOX (like it was earlier when i used courier). Now subfolders created at rootlevel or as subfolders of the inbox appear on rootlevel in thunderbird but they do not inherit the acl's from inbox. Is there an way to achive this? doveconf -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 ext4 auth_debug = yes auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_master_user_separator = % auth_mechanisms = plain login gssapi auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@% auth_username_format = %n auth_verbose = yes debug_log_path = syslog disable_plaintext_auth = no first_valid_gid = 998 first_valid_uid = 998 info_log_path = syslog mail_debug = yes mail_gid = 998 mail_home = /home/vmail/%u mail_location = maildir:/home/vmail/%u/mail mail_plugins = acl mail_shared_explicit_inbox = no mail_uid = 998 maildir_very_dirty_syncs = 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 ihave namespace { list = children location = maildir:/home/vmail/%%u/mail:INDEX=/home/vmail/%u/mail/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = maildir:/home/vmail/%u/mail prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf.ext driver = ldap } passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes } plugin { acl = vfile acl_anyone = allow acl_shared_dict = file:/home/vmail/.shared-mailboxes sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap lmtp sieve" service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0777 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap-postlogin { executable = script-login /etc/dovecot/acl-groups.sh user = $default_internal_user } service imap { executable = imap imap-postlogin } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/easy-rsa/keys/dovecot.crt ssl_key = </etc/easy-rsa/keys/dovecot.key userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap-userdb-groups.conf.ext driver = ldap } protocol imap { imap_client_workarounds = delay-newmail mail_plugins = acl imap_acl } protocol lmtp { mail_plugins = acl sieve }

1 4

[Dovecot] Problem with master user
by Jakub Krzyżewski 08 Nov '13

08 Nov '13

Hello. I have problem as below: Nov 8 10:41:52 store1 dovecot: auth: Debug: auth(master@example.com,::1,master,</qEuMafqyAAAAAAAAAAAAAAAAAAAAAAB>): Master user lookup for login: jkrzyz(a)example.com Nov 8 10:41:52 store1 dovecot: auth: Debug: passwd-file(master@example.com,::1,master,</qEuMafqyAAAAAAAAAAAAAAAAAAAAAAB>): lookup: user=master(a)example.com file=/etc/dovecot/master-use rs Nov 8 10:41:52 store1 dovecot: auth: Debug: password(master@example.com,::1,master,</qEuMafqyAAAAAAAAAAAAAAAAAAAAAAB>): Generating DIGEST-MD5 from user 'master', password 'test' Nov 8 10:41:52 store1 dovecot: auth: passdb(master@example.com,::1,master,</qEuMafqyAAAAAAAAAAAAAAAAAAAAAAB>): Master user logging in as jkrzyz(a)example.com Nov 8 10:41:52 store1 dovecot: auth: Debug: ldap(jkrzyz@example.com,::1,</qEuMafqyAAAAAAAAAAAAAAAAAAAAAAB>): pass search: base=dc=example,dc=com scope=subtree filter=(&(locMailActive=TRUE)(| (uid=jkrzyz@example.com)(uid=jkrzyz)(mailRoutingAddress=jkrzyz@example.com))) fields=mailRoutingAddress,userPassword Nov 8 10:41:52 store1 dovecot: auth: Debug: ldap(jkrzyz@example.com,::1,</qEuMafqyAAAAAAAAAAAAAAAAAAAAAAB>): result: mailRoutingAddress=jkrzyz(a)example.com userPassword=test2 Nov 8 10:41:52 store1 dovecot: auth: Debug: password(jkrzyz@example.com,::1,</qEuMafqyAAAAAAAAAAAAAAAAAAAAAAB>): Generating DIGEST-MD5 from user 'master', password 'test2' Nov 8 10:41:52 store1 dovecot: auth: Debug: password(jkrzyz@example.com,::1,</qEuMafqyAAAAAAAAAAAAAAAAAAAAAAB>): Credentials: d64221d543d7c9a809c7d6e424d87be8 Nov 8 10:41:52 store1 dovecot: auth: digest-md5(jkrzyz@example.com,::1,</qEuMafqyAAAAAAAAAAAAAAAAAAAAAAB>): password mismatch As you can see, password is check against user passdb and not passwd-file, where master's password is stored. Test is password of master user, test2 is password of jkrzyz Setting pass=yes or no makes no difference. What is wrong with my config? dovecot --version 2.1.7 dovecot.conf snippet: passdb { args = scheme=PLAIN /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } /etc/dovecot/master-users: master:{PLAIN}test master@example.com:{PLAIN}test

2 1

[Dovecot] how to calculate mail storage/traffic used
by Götz Reinicke - IT Koordinator 08 Nov '13

08 Nov '13

Hi, may be som mailserver admins on the list can give me som hint. Thats not dovecot related, but I know the knowledg here is enormous. We have to setup a server which gets a copy of all messages send and received by our mailserver as a 1:1 copy. Mails send to multiple recipients should be calculated and saved per user. (great if you usually have lost of mails send to groups of people.) So no dedublication should be used here. (e.g. save the message and refer the different recipients to it.) How can I calculate the current traffic in the best way to extrapolate the amount of space to be planed for the new server? We think to have a couples of days to be saved. Thanks for any hint or comment. Regards Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82 420 Fax +49 7141 969 55 420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt

2 3

[Dovecot] Solr clusters
by Timo Sirainen 07 Nov '13

07 Nov '13

Hi all, Has anyone implemented larger Dovecot+Solr clusters and would be willing to give some details about how it works for you? My understanding about it so far is: - SolrCloud isn’t usable with Dovecot. Replication isn’t useful, because nobody wants to pay for double the disk space for indexes that could be regenerated anyway. The autosharding isn’t very useful also, because: I think the shard keys could be created in two possible ways: a) Mails would be entirely randomly distributed across the cluster. This would make updates efficient, because the writes would be fully distributed across all servers. But I think it would also make reads somewhat inefficient, since all the servers would have to be searched and the results combined. Also if a server is lost, there’s no easy way to reindex back the missing data, because it would contain a piece of pretty much all the users’ data. b) Shard keys could be created so that the same user would typically go only to 1-2 servers. It would be possible (at least in theory) to find a broken server’s list of users and reindex only their data, but I’m not sure if this method is any easier than the non-SolrCloud setup. - Without SolrCloud you’d then need to shard the data manually. This would be easy enough to do by just assigning different users to different shards. But at some point the index is going to become too large and you need to add more shards and move some existing users to them. To keep the search performance good during the move, I guess this could be done with a script that does: 1) reindex user to new shard, 2) update userdb to point to new shard, 3) delete user from old shard, 4) doveadm fts rescan the user to remove any mails already deleted during the reindexing. - It seems that Solr index shouldn’t grow above 200 GB or the performance will be getting too bad? I’ve seen this in a few web pages. So each server should likely be running multiple separate Solr instances (shards). - http://www.hathitrust.org/blogs/large-scale-search/scaling-large-scale-sear… recommends NFS (or I guess any kind of a shared filesystem), which does seem to make sense. Since Dovecot wants to get instantly updated search results after indexing, I think it’s probably better not to separate the indexing and searching servers. - Would be interesting to know what kind of hardware your Solr servers currently have, how well they’re performing and what are the bottlenecks? From the above URL it appears that disk I/O is first, but if there’s enough of that available then CPU usage is second. I’m not quite sure where most of the memory goes - caching? - I’m guessing users are doing relatively few searches compared to how many new emails are being indexed/deleted all the time?

1 1

[Dovecot] how to display dovecot.index.cache
by ldaamandy 07 Nov '13

07 Nov '13

hello dovecot(a)dovecot.org: I want to see the contents of dovecot.index.cache . Is there any command can make it become visible character displayed ? the command idxview can displayed doveoct.index and logview can dispalyed dovecot.index.log but it seems no command to displays dovecot.index.cache for us. thanks amandy

3 6

[Dovecot] Postfix delivers mails to maildir and not to dovecot LDA for a virtual user
by Tru Pheenix 06 Nov '13

06 Nov '13

Hi I have been able to setup postfix and dovecot using postgres as the backend store with virtual user maps on Ubuntu 12.04 LTS Server. I have been following instructions from here: http://wiki2.dovecot.org/HowTo/DovecotPostgresql I haven't setup postfix to use saslauthd and PAM, instead I am using dovecot for SASL authentication. Rest of the table structures and query files are the same as from the wiki. SASL authentication works correctly for SMTP POP IMAP. I am able to send emails from a mail client such as Thunderbird with SASL authentication. However I am not able to receive emails for virtual users. I cannot figure out why. System users are getting their emails in the mail box correctly. Postfix fires the mailbox_command to hand over the mail to dovecot. This is how my *mail.log* looks when I send emails from an external domain: Nov 6 06:48:21 localhost postfix/smtpd[20053]: E075280C52: client= mail-ee0-f41.google.com[74.125.83.41] Nov 6 06:48:22 localhost postfix/cleanup[20064]: E075280C52: message-id=< CAJ+V0eCU891rSzSMVbcSy4zsRUk5GUp58b70Wv_WgZxLbKuyLw(a)mail.gmail.com> Nov 6 06:48:22 localhost postfix/qmgr[17492]: E075280C52: from=< me(a)gmail.com>, size=3124, nrcpt=1 (queue active) *Nov 6 06:48:22 localhost postfix/virtual[20066]: E075280C52: to=<someone(a)mydomain.com <someone(a)mydomain.com>>, relay=virtual, delay=0.85, delays=0.7/0.02/0/0.13, dsn=2.0.0, status=sent (delivered to maildir)* Nov 6 06:48:22 localhost postfix/qmgr[17492]: E075280C52: removed Nov 6 06:48:22 localhost postfix/smtpd[20053]: disconnect from mail-ee0-f41.google.com[74.125.83.41] Postfix seems to deliver the mail to maildir instead of the home directory of the virtual user. Incase of the system user, the logs indicate that the mailbox_command was fired and I do get to see the mail in the inbox. My postfix *main.cf <http://main.cf>*: alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes config_directory = /etc/postfix dovecot_destination_recipient_limit = 1 inet_interfaces = all *mailbox_command = /usr/lib/dovecot/deliver -c /etc/dovecot/conf.d/01-mail-stack-delivery.conf -m "${EXTENSION}"* mailbox_size_limit = 0 mydestination = localhost, localhost.localdomain, localhost myhostname = mydomain.com mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 readme_directory = no recipient_delimiter = + relayhost = smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtp_use_tls = yes smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) smtpd_recipient_restrictions = reject_unknown_recipient_domain, reject_unauth_pipelining, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/dovecot-auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_sender_restrictions = reject_unknown_sender_domain smtpd_tls_auth_only = yes smtpd_tls_cert_file = /root/certs/www.mydomain.com.pem smtpd_tls_key_file = /root/certs/www.mydomain.com.key smtpd_tls_mandatory_ciphers = medium smtpd_tls_mandatory_protocols = SSLv3, TLSv1 smtpd_tls_received_header = yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes tls_random_source = dev:/dev/urandom transport_maps = pgsql:/etc/postfix/transport.cf virtual_gid_maps = pgsql:/etc/postfix/gids.cf virtual_mailbox_base = /home virtual_mailbox_domains = mydomain.com *virtual_mailbox_maps = pgsql:/etc/postfix/mailboxes.cf <http://mailboxes.cf>* virtual_maps = pgsql:/etc/postfix/virtual.cf *virtual_transport = dovecot* virtual_uid_maps = pgsql:/etc/postfix/uids.cf I have included the virtual_transport parameter to indicate that dovecot is running as LDA. I have also included the pgsql query file in the virtual_mailbox_maps parameter. My *mailboxes.cf <http://mailboxes.cf> *file which points the email id of the virtual user to the appropriate mail path: user=mailreader password=secret dbname=mails table=postfix_mailboxes select_field=mailbox where_field=userid hosts=localhost My postfix *master.cf <http://master.cf>* file: smtp inet n - n - - smtpd pickup fifo n - - 60 1 pickup cleanup unix n - - - 0 cleanup qmgr fifo n - n 300 1 qmgr tlsmgr unix - - - 1000? 1 tlsmgr rewrite unix - - - - - trivial-rewrite bounce unix - - - - 0 bounce defer unix - - - - 0 bounce trace unix - - - - 0 bounce verify unix - - - - 1 verify flush unix n - - 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - - - - smtp relay unix - - - - - smtp showq unix n - - - - showq error unix - - - - - error retry unix - - - - - error discard unix - - - - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - - - - lmtp anvil unix - - - - 1 anvil scache unix - - - - 1 scache maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient} uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) *dovecot unix - n n - - pipe* * flags=DRhu user=vmailuser:vmailuser argv=/usr/lib/dovecot/deliver -f* * ${sender} -d ${recipient}* ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient scalemail-backend unix - n n - 2 pipe flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} I have included the dovecot LDA service line above so that postfix can deliver to virtual users as per: http://wiki2.dovecot.org/LDA/Postfix This is my *doveconf -n* output: # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-24-virtual i686 Ubuntu 12.04 LTS ext4 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login digest-md5 cram-md5 auth_verbose = yes mail_debug = yes *mail_location = maildir:/home/vmailuser/%d/%n/Maildir* 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 ihave passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </root/certs/www.mydomain.com.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </root/certs/www.mydomain.com.key userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_ssl = yes protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } I have setup *mail_location *to point to the home directory of vmailuser under which for the given domain the virtual users mail dir is created. However, the mails clearly don't seem to get delivered for the virtual user. Any help to fix this would be appreciated. Thanks! :) Regards Tru Pheenix

1 1

[Dovecot] Missing i_stream_unref in imap_msgpart_crlf_seek()?
by Tomasz Potega 06 Nov '13

06 Nov '13

Hi, imap_msgpart_crlf_seek() returns an error stream in case of problems in message_skip_virtual(). The original input stream is not being unreferenced, preventing destroy callbacks from being executed. Shouldn't we have an i_stream_unref(&input) here: src/lib-imap-storage/imap-msgpart.c: 398 if (message_skip_virtual(input, virtual_skip, &cr_skipped) < 0) { 399 errinput = i_stream_create_error(errno); 400 i_stream_set_name(errinput, i_stream_get_name(input)); 401 return errinput; 402 } ? Best regards, Tomasz Potęga [Wirtualna Polska] <http://www.wp.pl> Znajdziesz nas tutaj: [Wp na Facebooku] <https://www.facebook.com/WirtualnaPolska> [Wp na Twitterze] <https://twitter.com/wirtualnapolska> [Wp na SlideShare] <http://www.slideshare.net/wirtualnapolska> [Wp w Google+] <https://plus.google.com/+wppl> [Wp na YouTube] <https://www.youtube.com/user/wptvwppl> "WIRTUALNA POLSKA" Spółka Akcyjna z siedzibą w Gdańsku przy ul. Traugutta 115 C, wpisana do Krajowego Rejestru Sądowego - Rejestru Przedsiębiorców prowadzonego przez Sąd Rejonowy Gdańsk - Północ w Gdańsku pod numerem KRS 0000068548, o kapitale zakładowym 67.980.024,00 złotych opłaconym w całości oraz Numerze Identyfikacji Podatkowej 957-07-51-216.

2 1

[Dovecot] get_disconnect_reason() gets called with NULL ctx->litinput
by Tomasz Potega 06 Nov '13

06 Nov '13

Hi, I have found get_disconnect_reason() to be called with NULL ctx->litinput at times, making dovecot crash when accessing v_offset: src/imap/cmd-append.c: 83 switch (i_stream_read(client->input)) { 84 case -1: 85 /* disconnected */ 86 reason = get_disconnect_reason(ctx, ctx->litinput->v_offset); 87 cmd_append_finish(cmd->context); 88 /* Reset command so that client_destroy() doesn't try to call 89 cmd_append_continue_message() anymore. */ Best regards, Tomasz Potęga [Wirtualna Polska] <http://www.wp.pl> Znajdziesz nas tutaj: [Wp na Facebooku] <https://www.facebook.com/WirtualnaPolska> [Wp na Twitterze] <https://twitter.com/wirtualnapolska> [Wp na SlideShare] <http://www.slideshare.net/wirtualnapolska> [Wp w Google+] <https://plus.google.com/+wppl> [Wp na YouTube] <https://www.youtube.com/user/wptvwppl> "WIRTUALNA POLSKA" Spółka Akcyjna z siedzibą w Gdańsku przy ul. Traugutta 115 C, wpisana do Krajowego Rejestru Sądowego - Rejestru Przedsiębiorców prowadzonego przez Sąd Rejonowy Gdańsk - Północ w Gdańsku pod numerem KRS 0000068548, o kapitale zakładowym 67.980.024,00 złotych opłaconym w całości oraz Numerze Identyfikacji Podatkowej 957-07-51-216.

2 1

[Dovecot] ssl-params regeneration with dovecot 2.2.7
by Frank Elsner 06 Nov '13

06 Nov '13

Hello, after switching from version 2.2.7 to 2.2.7 I miss the loglines which say: ssl-params: Generating SSL parameters ssl-params: SSL parameters regeneration completed The configuration has not been changed and reads: | # 2.2.7: /usr/local/dovecot/etc/dovecot/dovecot.conf | # OS: Linux 2.6.35.14-106.fc14.i686.PAE i686 Fedora release 14 (Laughlin) ext3 | auth_mechanisms = plain login | default_vsz_limit = 512 M | first_valid_uid = 200 | last_valid_uid = 65534 | listen = * | lmtp_save_to_detail_mailbox = yes | login_greeting = c64.shuttle.de - IMAPs Service (dovecot) ready. | login_log_format_elements = %u %r %c | mail_location = maildir:/var/spool/mail/%u | mail_log_prefix = "%Us(%u,%r): " | mail_plugin_dir = /usr/dovecot/lib/dovecot/ | mail_plugins = notify quota fts fts_squat | namespace inbox { | inbox = yes | list = yes | location = | mailbox Drafts { | special_use = \Drafts | } | mailbox Gesendet { | special_use = \Sent | } | mailbox SPAM { | special_use = \Junk | } | mailbox Sent { | special_use = \Sent | } | mailbox Trash { | special_use = \Trash | } | prefix = | subscriptions = yes | type = private | } | passdb { | args = dovecot | driver = pam | } | plugin { | fts = squat | fts_squat = partial=4 full=10 | mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append | mail_log_fields = uid box from subject msgid size flags | mail_log_group_events = yes | quota = maildir:User quota | quota_rule = *:storage=2G | quota_rule2 = Trash:storage=+100M | } | postmaster_address = postmaster(a)moltke28.b.shuttle.de | protocols = imap | service anvil { | client_limit = 1027 | } | service auth { | unix_listener auth-client { | group = exim | mode = 0660 | user = exim | } | } | service imap-login { | inet_listener imap { | port = 143 | } | inet_listener imaps { | port = 993 | ssl = yes | } | process_limit = 512 | process_min_avail = 10 | } | service imap-postlogin { | executable = script-login /usr/local/sbin/dovecot-imap-post-login | } | service imap { | executable = imap imap-postlogin | } | service lmtp { | inet_listener lmtp { | address = 0.0.0.0 | port = 24 | } | } | service pop3-login { | inet_listener pop3 { | port = 110 | } | inet_listener pop3s { | port = 995 | ssl = yes | } | } | service pop3 { | process_limit = 1024 | } | ssl_cert = </usr/local/etc/c64.shuttle.de.CRT | ssl_key = </usr/local/etc/c64.shuttle.de-dovecot.KEY | ssl_parameters_regenerate = 1 hours | userdb { | driver = passwd | } | verbose_proctitle = yes | protocol lmtp { | mail_plugins = notify quota fts fts_squat | } | protocol lda { | mail_plugins = notify quota fts fts_squat | } | protocol imap { | imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags | imap_logout_format = [%i/%o] | mail_max_userip_connections = 0 | mail_plugins = notify quota fts fts_squat quota mail_log imap_quota listescape fts fts_squat | } What's going on? No more logging or no regeneration? Greetings, Frank Elsner

2 2

[Dovecot] 2.2.6 auth process crash using LMTP and LDAP on director.
by Olivier Girard 06 Nov '13

06 Nov '13

I'm upgrading my configuration to use director and lmtp for delivery. (doveconf -n at end of the mail). I use the same config for auth on mail backends and see no errors. My setup seem to work nicely but i have some auth process crashing when using lmtp protocol. Everything is working a sexpected then i've got 5-6 errors like this in logs and a crach of the auth process: dovecot: lmtp(47269): Error: passdb lookup(_mail_): Disconnected unexpectedly pid 47406 (auth), uid 143: exited on signal 11 Actually, i didn't configure to core dump. Do you think seting up lmtp protocol to static auth adding something like folow will be better for this problem? protocol lmtp { passdb { args = proxy=y nopassword=y driver = static } } Please note that my configuration is actually listening on inet fot LMTP but that the goal is to configure postfix on the same server and switch to socket, this expain the configuration of the service auth to provide a socket to postfix. Here is my director config: % doveconf -n # 2.2.6: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.4-RELEASE-p4 amd64 auth_cache_negative_ttl = 0 auth_cache_size = 16 M auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1 default_process_limit = 4000 director_mail_servers = 192.168.16.1 192.168.16.2 192.168.16.3 director_servers = 192.168.16.4 192.168.16.5 192.168.16.6 disable_plaintext_auth = no doveadm_port = 24245 info_log_path = syslog instance_name = director lmtp_proxy = yes mail_debug = 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 ihave passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size } service anvil { client_limit = 12003 } service auth-worker { process_min_avail = 10 user = $default_internal_user } service auth { client_limit = 16000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0666 user = $default_internal_user } user = $default_internal_user } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 192.168.16.4 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 24245 } } service imap-login { executable = imap-login director } service lmtp { inet_listener lmtp { address = * :: port = 24 } } service pop3-login { executable = pop3-login director } ssl_cert = </etc/ssl/cert/mail.univ-angers.fr.pem ssl_key = </etc/ssl/cert/mail.univ-angers.fr.key userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { auth_socket_path = director-userdb } protocol doveadm { auth_socket_path = director-userdb } local 192.168.16.0/24/24 { doveadm_password = mysecret } Last thing, in my config file, there is only one /24 on local network but this is another problem.

1 0

[Dovecot] Best way from Mbox to Maildir using 2.17?
by Regan Yelcich 06 Nov '13

06 Nov '13

Can someone advise the best way to convert mailboxes from Mbox to Maildir for Dovecot 2.17 on Ubuntu? Thanks.

9 20

Re: [Dovecot] Issue with postfix not handing over e-mails to dovecot
by Joseph Tam 05 Nov '13

05 Nov '13

Tru Pheenix writes: > posftconf output: https://gist.github.com/anonymous/7318863 > doveconf output: https://gist.github.com/anonymous/7318896 > tail -f /var/log/mail.* output (when receiving mail): > https://gist.github.com/anonymous/7318945 Unless these are exceeding long, you probably should inline the contents to save people from having to jump around to get the information to help you. It will also properly archive the context to the solution. >From your logs, it appears your mail system does not know what user is mapped to "someone(a)mydomain.com": Nov 5 13:21:06 localhost postfix/local[11185]: 5716D8007B: to=<someone(a)mydomain.com>, relay=local, delay=0.59, delays=0.57/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: "someone") I don't know whether this message is produced by postfix or by dovecot, but one thing I did notice is that your postfix configuration mailbox_command = /usr/lib/dovecot/deliver -c /etc/dovecot/conf.d/01-mail-stack-delivery.conf -m "${EXTENSION}" has upper-case "EXTENSION", whereas the Dovecot wiki uses lower case: http://wiki2.dovecot.org/LDA/Postfix If that's not it, maybe it's your SQL. You can also ask dovecot to look up user "somebody" and debug your way from there: doveadm user somebody Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] squat assertion result core dump with imap process
by Kui Zhang 05 Nov '13

05 Nov '13

Hello, Recently, we had a file system problem. After fsck we started to get some core dump with imap process. Nov 4 15:15:04 mail_server1 dovecot: imap(user(a)domain.tld): Panic: file squat-trie.c: line 293 (squat_trie_lock): assertion failed: (trie->fd != -1) Nov 4 15:15:04 mail_server1 dovecot: imap(user(a)domain.tld): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x4892a) [0x7fe8b7c9392a] -> /usr/lib/dovecot/libdovecot.so.0(+0x48976) [0x7fe8b7c93976] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7fe8b7c66faf] -> /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so(+0x4ef4) [0x7fe8b51d9ef4] -> /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so(squat_trie_build_deinit+0x9d2) [0x7fe8b51dcc02] -> /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so(+0x4150) [0x7fe8b51d9150] -> /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so(+0x41b1) [0x7fe8b51d91b1] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x6b7c) [0x7fe8b5a05b7c] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_backend_update_deinit+0x2c) [0x7fe8b5a05bfc] -> /usr/lib/dovecot/modules/lib10_quota_plugin.so(+0xb65a) [0x7fe8b642765a] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x419) [0x7fe8b7f22069] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync+0x46) [0x7fe8b7f224a6] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x87) [0x7fe8b7f22587] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x7fe8b7f614d1] -> dovecot/imap [user(a)domain.tld 204.174.223.223 UID](imap_sync_init+0x67) [0x419397] -> dovecot/imap [user(a)domain.tld204.174.223.223 UID](cmd_sync_delayed+0x1c7) [0x419637] -> dovecot/imap [user(a)domain.tld 204.174.223.223 UID](client_handle_input+0x1fd) [0x41131d] -> dovecot/imap [user(a)domain.tld 204.174.223.223 UID](client_input+0x5f) [0x411b7f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7fe8b7c9fb56] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7fe8b7ca0b8f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7fe8b7c9faf8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fe8b7c8b413] -> dovecot/imap [user(a)domain.tld 204.174.223.223 UID](main+0x2a4) [0x419dd4] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fe8b78dfead] -> dovecot/imap [user(a)domain.tld 204.174.223.223 UID Nov 4 15:15:04 mail_server1 dovecot: imap(user(a)domain.tld): Fatal: master: service(imap): child 28415 killed with signal 6 (core dumped) doveadm index -u user(a)domain.tld mailbox_name Removing index files and re index help with the crashes. From time to time we still get these in the log: Nov 5 10:52:53 mail_server1 dovecot: imap(user(a)domain.tld): Error: Corrupted squat uidlist file /media/drbd/user_name/mdbox/mailboxes/Drafts/dbox-Mails/dovecot.index.search.uids: wrong indexid Nov 5 11:40:00 mail_server1 dovecot: imap(user(a)domain.tld): Error: Corrupted squat uidlist file /media/drbd/user_name/mdbox/mailboxes/folder2/dbox-Mails/dovecot.index.search.uids: wrong indexid I am using: dovecot-dbg 2:2.1.16-0~auto+30 Thanks Kui.Z

1 0

[Dovecot] increased core dumps with v2.2.7
by Anand Kumria 05 Nov '13

05 Nov '13

Hi, After upgrading to v2.2.7 yesterday, I am starting to get a larger number of bugs occurring -- unfortunately I hadn't configured things to save core dumps (now done). But I am seeing things like: dovecot: imap(user(a)example.com): Fatal: master: service(imap): child 27931 killed with signal 11 (core dumped) kernel: [151706.763475] imap[4878]: segfault at 7fff53b0aff8 ip 00007fdc7ed65ece sp 00007fff53b0b000 error 6 in lib20_zlib_plugin.so[7fdc7ed61000+7000] dovecot: imap(user2(a)example.com): Fatal: master: service(imap): child 4870 killed with signal 11 (core dumped) As soon as I have more info., I'll let you know. A

2 2

[Dovecot] (Maybe stupid) question about selecting mailbox
by kjonca＠o2.pl 05 Nov '13

05 Nov '13

Does mailbox with "\NoSelect" can be select or examine? I'm not sure but IMVHO "select x" should not work. $/usr/lib/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE COMPRESS=DEFLATE] Logged in as kjonca 2 LIST "x" "*" * LIST (\Noselect \HasChildren) "/" "x" * LIST (\HasNoChildren) "/" "x/y" 2 OK List completed. 3 SELECT x * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1376977764] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [NOMODSEQ] No permanent modsequences 3 OK [READ-WRITE] Select completed. 4 logout IMAP(kjonca): Info: Disconnected: Logged out in=35 out=813 * BYE Logging out 4 OK Logout completed. doveconf -n # 2.1.17 (d463fab6db95): /etc/dovecot/dovecot.conf # OS: Linux 3.8.9+1 x86_64 Debian wheezy/sid auth_debug = yes auth_mechanisms = plain digest-md5 cram-md5 login auth_username_format = %n auth_verbose = yes listen = alfa log_path = /var/log/dovecot mail_debug = yes mail_location = maildir:~/Mail/1:LAYOUT=fs:INBOX=~/Mail/1/INBOX mail_log_prefix = "%Us(%u): " mail_plugins = zlib passdb { args = scheme=PLAIN /etc/security/dovecot.pwd driver = passwd-file } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change save mail_log_fields = uid box msgid size from flags sieve = ~/.dovecot.sieve sieve_execute_bin_dir = %h/sieve/bin sieve_execute_exec_timeout = 86400s sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.filter sieve_filter_bin_dir = %h/sieve/bin sieve_filter_exec_timeout = 86400s sieve_pipe_bin_dir = %h/sieve/bin sieve_pipe_exec_timeout = 86400s sieve_plugins = sieve_extprograms } protocols = " imap lmtp" service auth { user = root } ssl = no ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } protocol lmtp { mail_plugins = zlib sieve } protocol lda { deliver_log_format = msgid=%m: %$ log_path = ~/log/deliver.log mail_plugins = zlib sieve postmaster_address = root@localhost } protocol imap { mail_max_userip_connections = 20 mail_plugins = zlib imap_zlib mail_log notify acl } -- http://blogdebart.pl/2009/12/22/mamy-chorych-dzieci/ The goal of Computer Science is to build something that will last at least until we've finished building it.

2 2

[Dovecot] Message parser loops on certain messages (e.g. with a trailing CR character)
by Tomasz Potega 05 Nov '13

05 Nov '13

Hi, dovecot's message parser enters an endless loop when fed with certain multipart messages with stray CR characters. parse_next_body_to_boundary() assumes the '\r' might be the beginning of a boundary line, reducing the block size by one: src/lib-mail/message-parser.c: 404 /* no linefeeds in this block. we can just skip it. */ 405 ret = 0; 406 if (block_r->data[block_r->size-1] == '\r') { 407 /* this may be the beginning of the \r\n--boundary */ 408 block_r->size--; 409 } For a block size of 1 (e.g. the trailing '\r' character), dovecot ends up processing zero-sized blocks, calling message_parser_read_more() without skipping the input stream: ... #6 0x00007f94f49374c7 in i_stream_read (stream=0xbe2fc8) at istream.c:167 #7 0x00007f94f49383d5 in i_stream_read_data (stream=0xbe2fc8, data_r=0x7fff2141d6b0, size_r=0x7fff2141d6b8, threshold=1) at istream.c:497 #8 0x00007f94f4918c2b in message_parser_read_more (ctx=0xbe7c10, block_r=0x7fff2141d6a0, full_r=0x7fff2141d667) at message-parser.c:128 #9 0x00007f94f491af67 in message_parser_parse_next_block (ctx=0xbe7c10, block_r=0x7fff2141d6a0) at message-parser.c:1012 #10 0x00007f94f491b2fb in message_parser_parse_body (ctx=0xbe7c10, hdr_callback=0x7f94f4c69a75 <parse_bodystructure_part_header>, context=0xbf0450) at message-parser.c:1075 #11 0x00007f94f4c6a876 in index_mail_parse_body (mail=0xbecd00, field=MAIL_CACHE_IMAP_BODYSTRUCTURE) at index-mail.c:895 #12 0x00007f94f4c6aedb in index_mail_parse_bodystructure (mail=0xbecd00, field=MAIL_CACHE_IMAP_BODYSTRUCTURE) at index-mail.c:1046 #13 0x00007f94f4c6b4a5 in index_mail_get_special (_mail=0xbecd00, field=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=0x7fff2141d958) at index-mail.c:1170 #14 0x00007f94f4bfab53 in maildir_mail_get_special (_mail=0xbecd00, field=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=0x7fff2141d958) at maildir-mail.c:570 #15 0x00007f94f4c36ea1 in mail_get_special (mail=0xbecd00, field=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=0x7fff2141d958) at mail.c:269 #16 0x000000000041c5d7 in fetch_bodystructure (ctx=0xbd6a48, mail=0xbecd00, context=0x0) at imap-fetch.c:678 ... You will find a sample message attached to this mail. I have added a check to see if the parser is past the EOF (and omit reducing the block size then) as a band-aid fix, but this might call for a more elegant solution. Best regards, Tomasz Potêga [Wirtualna Polska] <http://www.wp.pl> Znajdziesz nas tutaj: [Wp na Facebooku] <https://www.facebook.com/WirtualnaPolska> [Wp na Twitterze] <https://twitter.com/wirtualnapolska> [Wp na SlideShare] <http://www.slideshare.net/wirtualnapolska> [Wp w Google+] <https://plus.google.com/+wppl> [Wp na YouTube] <https://www.youtube.com/user/wptvwppl> "WIRTUALNA POLSKA" Spółka Akcyjna z siedzibą w Gdańsku przy ul. Traugutta 115 C, wpisana do Krajowego Rejestru Sądowego - Rejestru Przedsiębiorców prowadzonego przez Sąd Rejonowy Gdańsk - Północ w Gdańsku pod numerem KRS 0000068548, o kapitale zakładowym 67.980.024,00 złotych opłaconym w całości oraz Numerze Identyfikacji Podatkowej 957-07-51-216.

2 1

[Dovecot] infinite loop (causing crash) whilst closing connection
by Anand Kumria 05 Nov '13

05 Nov '13

Hi Timo, As a follow-up to my earlier email, I've managed to get a few backtraces now. #305439 o_stream_close (stream=0x1680c10) at ostream.c:85 #305440 0x00007ff222f70f3c in o_stream_zlib_send_outbuf (zstream=0x1680b80) at ostream-zlib.c:97 #305441 0x00007ff222f70fef in o_stream_zlib_send_flush (zstream=0x1680b80) at ostream-zlib.c:182 #305442 0x00007ff222f711cb in o_stream_zlib_flush (stream=<optimized out>) at ostream-zlib.c:222 #305443 0x00007ff2243f142d in o_stream_flush (stream=0x1680c10) at ostream.c:147 #305444 0x00007ff222f70ddf in o_stream_zlib_close (stream=0x1680b80, close_parent=true) at ostream-zlib.c:35 #305445 0x00007ff2243f12ce in o_stream_close_full (close_parents=true, stream=0x1680c10) at ostream.c:49 #305446 o_stream_close (stream=0x1680c10) at ostream.c:85 #305447 0x00007ff222f70f3c in o_stream_zlib_send_outbuf (zstream=0x1680b80) at ostream-zlib.c:97 #305448 0x00007ff222f70fef in o_stream_zlib_send_flush (zstream=0x1680b80) at ostream-zlib.c:182 #305449 0x00007ff222f711cb in o_stream_zlib_flush (stream=<optimized out>) at ostream-zlib.c:222 #305450 0x00007ff2243f142d in o_stream_flush (stream=0x1680c10) at ostream.c:147 #305451 0x00007ff222f70ddf in o_stream_zlib_close (stream=0x1680b80, close_parent=true) at ostream-zlib.c:35 #305452 0x00007ff2243f12ce in o_stream_close_full (close_parents=true, stream=0x1680c10) at ostream.c:49 #305453 o_stream_close (stream=0x1680c10) at ostream.c:85 #305454 0x00007ff222f70f3c in o_stream_zlib_send_outbuf (zstream=0x1680b80) at ostream-zlib.c:97 #305455 0x00007ff222f710ff in o_stream_zlib_send_flush (zstream=0x1680b80) at ostream-zlib.c:193 #305456 0x00007ff222f71491 in o_stream_zlib_sendv (stream=0x1680b80, iov=0x7fff6b3e1870, iov_count=1) at ostream-zlib.c:257 #305457 0x00007ff2243f1785 in o_stream_sendv (stream=0x1680c10, iov=0x7fff6b3e1870, iov_count=1) at ostream.c:229 #305458 0x00007ff2243f186f in o_stream_nsendv (stream=0x1680c10, iov=<optimized out>, iov_count=<optimized out>) at ostream.c:263 #305459 0x00007ff2243f189a in o_stream_nsend (stream=<optimized out>, data=<optimized out>, size=<optimized out>) at ostream.c:255 #305460 0x00000000004157f0 in client_send_tagline (cmd=<optimized out>, data=0x423c82 "OK Close completed.") at imap-client.c:388 #305461 0x000000000040c833 in cmd_close (cmd=0x167c4d0) at cmd-close.c:37 #305462 0x000000000041707d in command_exec (cmd=0x167c4d0) at imap-commands.c:158 #305463 0x0000000000416110 in client_command_input (cmd=0x167c4d0) at imap-client.c:780 #305464 0x00000000004161f5 in client_command_input (cmd=0x167c4d0) at imap-client.c:841 #305465 0x000000000041649d in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x167b8f0) at imap-client.c:879 #305466 client_handle_input (client=0x167b8f0) at imap-client.c:891 #305467 0x00000000004165de in client_continue_pending_input (client=0x167b8f0) at imap-client.c:715 #305468 0x000000000040ed89 in idle_client_input (ctx=<optimized out>) at cmd-idle.c:112 #305469 0x00007ff2243e8686 in io_loop_call_io (io=0x16e67e0) at ioloop.c:387 #305470 0x00007ff2243e953f in io_loop_handler_run (ioloop=<optimized out>) at ioloop-epoll.c:220 #305471 0x00007ff2243e8198 in io_loop_run (ioloop=0x165d730) at ioloop.c:411 #305472 0x00007ff224397b93 in master_service_run (service=0x165d5c0, callback=<optimized out>) at master-service.c:566 #305473 0x000000000040af18 in main (argc=1, argv=0x165d390) at main.c:400 Let me know if you need further information. This is with dovecot v2.2.7 (1:2.2.7.0-1) Thanks, Anand

1 0

[Dovecot] Config problem: want SSL + local roundcube
by Rich 05 Nov '13

05 Nov '13

Hi, Have used dovecot for many years, happy that it worked well without me needing to do anything much! But since the upgrade from v1 to v2.1.7-7 I've come across some config probs. I want IMAP and to force TLS for all internet connections. However, I run RoundCube on the same server (over https) and this needs access too, but this doesn't need to be TLS because it's local anyway. The auto-config update script made some changes, it added the following to force SSL. service imap-login { inet_listener imap { port = 0 } } ssl = required But this seems to forbid the local roundcube service from logging in. Can anyone help me with my config? I had a stab, adding the following, but it didn't work. Was a complete guess anyway! remote 127.0.0.1 { ssl = no service imap-login { inet_listener imap { port = 143 } } } Here's my full config: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 7.2 ext3 auth_default_realm = artfulrobot.com log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/virtual/%d/%n mail_privileged_group = mail passdb { args = username_format=%n /etc/exim4/virtual_domains/%d/passwords driver = passwd-file } protocols = imap service auth { unix_listener auth-client { group = Debian-exim mode = 0660 } user = root } service imap-login { inet_listener imap { port = 0 } } ssl = required ssl_cert = </etc/ssl/certs/mail.artfulrobot.com-with-chain.crt ssl_key = </etc/ssl/private/mail.artfulrobot.com.key userdb { args = uid=1001 gid=1001 driver = static } userdb { driver = passwd } Thanks, Rich

3 5

[Dovecot] [bug] ssl-params hangs when FIPS is enabled
by Michal Hlavinka 05 Nov '13

05 Nov '13

Hi, we found a bug in ssl-params. It calls openssl DH generator for 512 and 1024 bits, but in FIPS mode, openssl won't generate anything for less than 1024, so it fails with: error:0506A06E:Diffie-Hellman routines:DH_BUILTIN_GENPARAMS:key size too small but when DH generator fails, ssl-params hangs forever in io_loop_run: __epoll_wait_nocancel() io_loop_handler_run(..) at ioloop-epoll.c:176 io_loop_run(..) at ioloop.c:406 master_service_run(..) at master-service.c:566 main(..) at main.c:156 Getting system in FIPS mode can be a little tricky, but DH_generator simulated failure can do the trick. Just change ssl-params/ssl-params-openssl.c:generate_dh_paramaters:39 - if (dh == NULL) { + if (1 || dh == NULL) { and when you run ssl-params (with no ssl-parameters.dat), it hangs. Let me know if you need more information. Regards, Michal Hlavinka

2 3

[Dovecot] Issue with postfix not handing over e-mails to dovecot
by Tru Pheenix 05 Nov '13

05 Nov '13

Hello! I have installed postfix with dovecot and postgresql. I have set up SASL authentication for postfix and dovecot and been able to test them successfully. I am able to send sasl authenticated emails through smtpd on postfix using a mail client like Thunderbird. However, now I am unable to receive any e-mails. When I respond to the emails, I get a not delivered failure from postfix. I cannot figure out why postfix is not handing over the e-mails to dovecot. So here are some links to follow: posftconf output: https://gist.github.com/anonymous/7318863 doveconf output: https://gist.github.com/anonymous/7318896 tail -f /var/log/mail.* output (when receiving mail): https://gist.github.com/anonymous/7318945 Any help to solve this would be highly appreciated. Regards Tru Pheenix

1 0

Re: [Dovecot] dovecot Digest, Vol 127, Issue 7
by DV Henkel-Wallace 05 Nov '13

05 Nov '13

> Date: Tue, 5 Nov 2013 08:22:57 +0100 (CET) > From: Steffen Kaiser <skdovecot(a)smail.inf.fh-brs.de> > >> >> My specific application: I am running spamassassin and would like users >> to be able to submit spam (and ham) directly by moving it into special >> folders. > I did this before switching to antispam. > I use antispam with spool2dir now, that central directory has a inotify > watcher that trains the messages instantly. This is a great idea. In my case I think I will get away with a five minute cron job since the pickup latency should be manageable to the users and there is less to install. But I like in principle the idea of an immediate, fs-driven trigger, which would probably use fewer CPU cycles in the aggregate. > [...]all my users moved messages into spam/yes, > but copied them into spam/no Unfortunately I can't rely on users getting this right, much less understanding the difference between copy and move semantics. And I'm probably not going to be able to upgrade my users. Thanks for your advice! -d

1 0

[Dovecot] s it safe to manipulate Maildir files directly?
by DV Henkel-Wallace 05 Nov '13

05 Nov '13

> Date: Tue, 5 Nov 2013 08:40:31 +0100 > From: Oli Schacher <dovecot(a)lists.wgwh.ch> > > On Mon, 4 Nov 2013 21:49:59 -0800 > David Henkel-Wallace <gumby(a)henkel-wallace.org> wrote: > >> Having the cron job find the messages and train spamassassin is no >> problem. The question is how to move the messages. Is it safe to >> simply rename the files from my cron job? > [...] >> If I have to go through to Dovecot I am afraid I'd need the user's >> credentials, which is not appropriate. > > you can do all this with doveadm scripts. Oli, thanks for the suggestion. It hadn't occured to me to consider doveadm. That's exactly the right tool. Regards, David

1 0

[Dovecot] Is it safe to manipulate Maildir files directly?
by David Henkel-Wallace 05 Nov '13

05 Nov '13

Dovecoters, is it safe to manipulate files in Maildir/xxx directly or will Dovecot become unstable if I don't make these changes by talking to Dovecot and having it make the changes? (I'm running 2.1.7 under Wheezy, IMAP only) My specific application: I am running spamassassin and would like users to be able to submit spam (and ham) directly by moving it into special folders. A cron job can then find it and take action: feed spam messages to the bayesian trainer and then delete them; feed ham messages to the trainer and then move them into ~/Maildir/cur/ Having the cron job find the messages and train spamassassin is no problem. The question is how to move the messages. Is it safe to simply rename the files from my cron job? The dovecot wiki implies that dovecot will notice a change in mtime and deal with it safely. Am I reading this correctly? Changing a message flags (i.e. name) and/or directory will change mtime. If I have to go through to Dovecot I am afraid I'd need the user's credentials, which is not appropriate. Thanks! -d

3 2

[Dovecot] Stuck with authentication for my dovecot installation.
by Tru Pheenix 04 Nov '13

04 Nov '13

Hello! I have been following instructions from here to setup dovecot along with postfix and postgresql and sasl2. I try to login but I keep getting the following messages in /var/log/mail.log Nov 2 19:51:39 localhost dovecot: ssl-params: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:51:39 localhost dovecot: anvil: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:51:39 localhost dovecot: config: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:51:39 localhost dovecot: log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:51:39 localhost dovecot: master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:51:44 localhost dovecot: master: Dovecot v2.0.19 starting up (core dumps disabled) Nov 2 19:53:11 localhost dovecot: master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:53:11 localhost dovecot: log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:53:11 localhost dovecot: master: Dovecot v2.0.19 starting up (core dumps disabled) Nov 2 19:53:29 localhost dovecot: auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Nov 2 19:53:29 localhost dovecot: auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_pgsql.so Nov 2 19:53:29 localhost dovecot: auth: Debug: auth client connected (pid=12718) Nov 2 19:53:29 localhost dovecot: auth: pgsql(localhost): Connected to database mails Nov 2 19:53:41 localhost dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011lip=127.0.0.1#011rip=127.0.0.1#011lport=143#011rport=58759#011resp=<hidden> Nov 2 19:53:41 localhost dovecot: auth: Debug: sql(someone(a)mydomain.com,127.0.0.1): query: SELECT userid as user, password FROM users WHERE userid = 'someone(a)mydomain.com' Nov 2 19:53:41 localhost dovecot: auth: sql(someone(a)mydomain.com,127.0.0.1): Password mismatch My doveconf -n gives the following output # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-24-virtual i686 Ubuntu 12.04 LTS auth_debug = yes auth_verbose = yes passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } passdb { driver = pam } protocols = " imap pop3" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } userdb { driver = passwd } Please let me know what is wrong. Regards Tru Pheenix

2 2

[Dovecot] backup maildir mailbox bugs
by Anand Kumria 04 Nov '13

04 Nov '13

Hi, Using dovecot v2.2.5.5, I get the following: $ doveadm -v backup -R -u user(a)example.com maildir:/home/rsync/ example.com/user/Maildir/ [...] dsync(user(a)example.com): Panic: file dsync-mailbox-export.c: line 228 (export_save_change_get): assertion failed: (change->type == DSYNC_MAIL_CHANGE_TYPE_FLAG_CHANGE) dsync(user(a)example.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x59e6a) [0x7f91ad185e6a] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f91ad185f2a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f91ad144b89] -> doveadm [user(a)example.com Printing Quotes send:mailbox recv:mailbox](dsync_mailbox_export_init+0x8b8) [0x434028] -> doveadm [ user(a)example.com Printing Quotes send:mailbox recv:mailbox](dsync_brain_sync_mailbox_open+0x233) [0x42ba83] -> doveadm [ user(a)example.com Printing Quotes send:mailbox recv:mailbox](dsync_brain_slave_recv_mailbox+0x125) [0x42c615] -> doveadm [ user(a)example.com Printing Quotes send:mailbox recv:mailbox](dsync_brain_run+0x369) [0x42a929] -> doveadm [user(a)example.comPrinting Quotes send:mailbox recv:mailbox]() [0x42881b] -> doveadm [ user(a)example.com Printing Quotes send:mailbox recv:mailbox]() [0x411ad7] -> doveadm [user(a)example.com Printing Quotes send:mailbox recv:mailbox](doveadm_mail_try_run+0x260) [0x4127a0] -> doveadm [ user(a)example.com Printing Quotes send:mailbox recv:mailbox](main+0x3f0) [0x4116c0] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f91acd8e76d] -> doveadm [user(a)example.com Printing Quotes send:mailbox recv:mailbox]() [0x4118bd] Other lines emitted were Info lines indicating what message was being processed. Unfortunately this appears to stop the backup dead in it's tracks. Suggestions on how to proceed? I was (originally) doing this as an IMAP to IMAP copy, and when that failed I managed to get the raw Maildir. Now I appear stuck with that too. Regards, Anand -- “Don’t be sad because it’s over. Smile because it happened.” – Dr. Seuss

2 4

[Dovecot] v2.2.7 released
by Timo Sirainen 04 Nov '13

04 Nov '13

http://dovecot.org/releases/2.2/dovecot-2.2.7.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.7.tar.gz.sig * Some usage of passdb checkpassword could have been exploitable by local users. You may need to modify your setup to keep it working. See http://wiki2.dovecot.org/AuthDatabase/CheckPassword#Security + auth: Added ability to truncate values logged by auth_verbose_passwords (see 10-logging.conf comment) + mdbox: Added "mdbox_deleted" storage, which can be used to access messages with refcount=0. For example: doveadm import mdbox_deleted:~/mdbox "" mailbox inbox subject oops + ssl-params: Added ssl_dh_parameters_length setting. - master process was doing a hostname.domain lookup for each created process, which may have caused a lot of unnecessary DNS lookups. - dsync: Syncing over 100 messages at once caused problems in some situations, causing messages to get new UIDs. - fts-solr: Different Solr hosts for different users didn't work.

4 4

[Dovecot] Shared mailbox help needed
by Alex Ferrara 04 Nov '13

04 Nov '13

Hi everyone, I am in the middle of a migration from Cyrus 2.4 to Dovecot 2.1.7, and I have everything mostly working. I set up Dovecot to authenticate against Active Directory (Samba4) using PAM and SSSD, and have also used the fantastic cyrus2dovecot perl script to do a test migration of all our mail, and that is now working flawlessly. I have the issue of shared IMAP accounts to deal with, and I am a little stuck. I see that Dovecot is very flexible, and I think I am getting stuck in this flexibility. I thought that if I explain what I am trying to achieve, someone might point me in the right direction. In the Cyrus regime, we have several imap accounts that are shared with a group of people. These groups are actual unix groups that actual unix users are a member of. If we want a person to access a mailbox, we add them to the group and then at next login, it pops up in Thunderbird automatically. SSSD does, from what I can tell, a decent job of binding to AD and mapping AD users to unix users, but since not all of the users have an NIS uid in AD, I decided to use a static mapping. This might have been the wrong decision, I am not sure. userdb { driver = static args = uid=900 gid=900 home=/mnt/mail/%u allow_all_users=yes } It probably isn't important at this stage, but the mail spool is stored on an NFS server and the indexes are stored locally. Thanks in advance, Alex Ferrara Director Receptive IT Solutions

1 0

Re: [Dovecot] Doveadm with a 2nd Instance
by Chris Lasater 03 Nov '13

03 Nov '13

While testing some more I found out something else. I have an alias set for doveadm so it was running with sudo and that ended up being part of the issue. If doveadm is run as a regular user then the problem goes away [user@server ~]$ doveadm -i Director log find Debug: /home/user/apps/logs/director/director_debug.log Info: /home/user/apps/logs/director/director_info.log Warning: /home/user/apps/logs/director/director.log Error: /home/user/apps/logs/director/director.log Fatal: /home/user/apps/logs/director/director.log [user@server ~]$ sudo doveadm -i Director log find Debug: /home/user/apps/logs/dovecot_debug.log Info: /home/user/apps/logs/dovecot_info.log Warning: /home/user/apps/logs/dovecot.log Error: /home/user/apps/logs/dovecot.log Fatal: /home/user/apps/logs/dovecot.log Also if I run "sudo doveadm stop" to stop the main instance, I now have the ability to use the -i Director using sudo. Unfortunately this makes it difficult to manage two instances. Does anyone have an idea of getting this to work with sudo? Chris

2 2

[Dovecot] Encryption solution for messages at rest
by Douglas Mortensen 03 Nov '13

03 Nov '13

Hi, We have clients with various security & compliance requirements. Although not required, it would be ideal to have messages encrypted at rest. We already use SSL/TLS to secure the transmission of most email. However, it would be nice to have them encrypted sitting on our server. Is anyone doing this? I think that ideally, rather than full-disk encryption, we should use an encryption that encrypts the actual email messages as they sit on our file system. This way even if we ever had our server breached by an attacker, they wouldn't be able to do anything with the messages. However, this would also mean that if the attacker can't decrypt the files, than dovecot and postfix still would need to. This means that the encryption key would need to be available to the dovecot deamon. We'd either need to have it in a file that is restricted to access only by dovecot (less secure), or use an encryption passphrase for the certificate which would have to be typed in manually each time that dovecot starts or restarts (more secure, but also more work and possibility of disruption because the server can't restart gracefully without a human being having to be present [although I don't think we have issues with unexpected restarts anyway]). Is anyone doing anything like this with dovecot? Thanks!! - Doug Mortensen Network Consultant Impala Networks Inc CCNA, MCSA, Security+, A+ Linux+, Network+, Server+ A.A.S. Information Technology . www.impalanetworks.com P: (505) 327-7300 F: (505) 327-7545

6 6

[Dovecot] Assertion error in Dovecot 2.2.6
by Mark Sapiro 03 Nov '13

03 Nov '13

Background. A while back I upgraded my phone to one currently using Android 4.1.2 and K9 mail 4.409. This phone/MUA combination seems at times to go crazy making IMAP connections. At first, I had mail_max_userip_connections = 30 (my largest imap account has 19 folders). The issue I had at that time was multiple errors like Oct 14 17:45:16 sbh16 dovecot: imap-login: Maximum number of connections from user+IP exceeded (mail_max_userip_connections=30): user=<xxx>, method=PLAIN, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, TLS, session=<c63x5bzowQBi0uQR> I then set mail_max_userip_connections = 50 This greatly reduced but didn't completely eliminate these messages, but then I would see multiple Oct 31 16:13:40 sbh16 dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped and Oct 31 16:13:40 sbh16 dovecot: imap-login: Disconnected: Connection queue full (no auth attempts in 4 secs): user=<>, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, TLS handshaking, session=<s26xmRHqVQBi0uQR> followed finally by Oct 31 16:13:40 sbh16 dovecot: imap-login: Panic: file client-common.c: line 190 (client_destroy): assertion failed: (!client->authenticating) Oct 31 16:13:40 sbh16 dovecot: auth: Warning: auth client 19669 disconnected with 1 pending requests: EOF Oct 31 16:13:40 sbh16 dovecot: imap-login: Fatal: master: service(imap-login): child 19669 killed with signal 6 (core not dumped - add -D parameter to service imap-login { executable } I then set default_process_limit = 200, and things seem to have settled down, but I thought the panic should be reported. Possibly this is relevant - the above only seem to occur when the phone is connecting via wifi and possibly only when the phone has just switched from the phone data network to wifi. Current doveconf -n # 2.2.6: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms = plain apop login auth_worker_max_count = 5 default_process_limit = 200 mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl dotlock 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 = /usr/local/etc/dovecot.passwd driver = passwd-file } passdb { driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = </etc/httpd/conf/ssl/combined.crt ssl_key = </etc/httpd/conf/ssl/www.grizz.org.key userdb { driver = passwd } protocol imap { mail_max_userip_connections = 50 } -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

[Dovecot] METADATA for v2.2.7
by Timo Sirainen 02 Nov '13

02 Nov '13

In case someone wants to try: http://hg.dovecot.org/dovecot-2.2/rev/0a08efeb3f40 The commit message lists the TODO. So for example if you want to enable it just for webmail (because quota limits aren’t there yet): mail_attribute_dict = file:%h/dovecot-attributes local 10.0.0.0/24 { imap_metadata = yes } Compared to the old metadata plugin, there are some improvements: - Uses lib-storage attributes internally, which means: - dsync replicates METADATA - it will be easy to add support for untagged METADATA notifications to clients when they change - SETMETADATA atomically either updates all or none of the changes Things that work in the METADATA code, but still require lib-dict changes to work properly: - Values with unlimited sizes - Values with binary data (NULs)

1 0