- dovecot - dovecot.org

[Dovecot] Default mail folders.
by Bruce Markey 11 Sep '13

11 Sep '13

Just want to make sure before I set this up. I read that the autocreate plugin is deprecated and to use "Mailbox settings" as listed here http://wiki2.dovecot.org/MailboxSettings. If that is correct then do I just add those mailbox blocks in /etc/dovecot/conf.d/10-mail.conf? Lastly, will "sent items" auto populate with sent items or is there something else that needs to be done. I just switched over from courier and I'm still getting used to where/how things are done. Thanks Bruce -- Please use PGP, ENCRYPT everything. For information about acquiring a secryption.com account, email me. My public key: https://www.secryption.com/BruceMarkey.asc or https://keyserver.pgp.com

3 3

[Dovecot] Sieve, vacation, company (domain-wide) message possible?
by Charles Marcus 10 Sep '13

10 Sep '13

Hello, I've been using vacation.pl from postfixadmin for many years, and since the most recent modification that allows me to specify my own strings to test for for when NOT to send a message, I'm extremely happy with it (no more auto-responses to linked-in/facebook crap, etc)... But, there is one thing I'd like to be able to do that it can't do, and there hasn't been any positive response about implementing it, so I'm asking about if this is possible to do with sieve right now, and if not, how hard would it be to implement... What I'd like is to be able to set a company (domain-wide) auto-response for when our company is closed for holidays... more specifically, extra holidays (often the boss will close an extra day for an extra long weekend). He has asked more than once about setting an auto-response for *everyone* during these periods... Thanks, -- Best regards, */Charles/*

5 7

[Dovecot] Sieve Filter global vs user specific
by inkubus 10 Sep '13

10 Sep '13

Hi@all! I'm actually fighting to make sieve in dovecot work and made quite a success by now. However, I still fail at the following constellation: Background: I'm a Mail Admin of a small IT department and we are already using Dovecot as LDA with a filtering server. Any user can easily create filter rules that apply to him (to make it easier for my colleagues we use the Roundcube plugin for rule design). I can formulate global rules that apply to all. Individual users create their rules for redirectiong mails home (a la redirect: copy "users(a)theirhomes.de";) According to the policy of my company, certain file types (eg avi, mp4, mp3, wav, etc.) must NOT be sent out to the internet. But our phone system does INTERNALLY just that - receiving calls in absence of the user it sends mails with attachments MP3 (the spoken message). These mails must of course not be forwarded outside. I also created a global rule, which supresses the delivery of these mails (using the stop command), But after my global rule follows the user specific rule and the message ist sent anyway. QUESTION: Can cause dovecot somehow not to follow the user specific rules that apply to a message after going through my global ones? The mail has to remain directly in the inbox (and must not be forwarded by the user specific filter aftwerwards) My configuration: dovecot.conf (excerpt): plugin { sieve = /home/%n/.dovecot.sieve sieve_dir = /home/%n/.mailstore/sieve sieve_global_dir = /etc/dovecot/sieve/ sieve_before = /etc/dovecot/sieve/global } /etc/dovecot/sieve/global: require ["vacation","copy","fileinto","body","imap4flags"]; # rule:[Redirect] if anyof(header :contains "From" "f...ing.telefonanlage(a)firma.intern", header :contains "Subject" "Sprachnachricht") { stop; } user specific rules are as follows # rule:[Redirect] if true { redirect :copy "users(a)theirhomes.de"; } I hope my English is understandable (got quite a cold andfighting to keep my eyes open so my English is not the best today ;-) ) I'm sure the solution for this problem is a nobvious & simple one but I'm having my blond moments today... Any help would be appreciated! yours Sven P.S. Klar bin ich mir bewusst, dass einfach die Benutzerfilter aufgebohrt werden könnten. Da aber nicht alle Kollegen... sagen wir entsprechend firm... sind, würde ich den Pflegeaufwand gern gering halten und dieses Ausnehmen vo der weiterleitung zentralisieren. -- View this message in context: http://dovecot.2317879.n4.nabble.com/Sieve-Filter-global-vs-user-specific-t… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] Proxy and Master Config
by Regan Yelcich 10 Sep '13

10 Sep '13

I'm just sitting down to configure a Proxy & Master Dovecot setup with Postfix and virtual users. I have read plenty about how to configure Dovecot as a proxy, but I'm unclear what's required on the "master" end. Does the master need the -pop and -imap scripts? or does the proxy handle that and call -deliver on the master? Can anyone explain the basic setup so I get it right. Thanks.

1 0

Re: [Dovecot] Is dovecot locking properly?
by Joseph Tam 10 Sep '13

10 Sep '13

Scott Galambos writes: > Hello, I'm attempting to move form qpopper 4.1 to Dovecot 2.2.5 on > Linux. When a user checks POP mail qpopper seems to make a > .username.pop temporary file in the same /var/mail directory as the mbox > INBOX file. Watching what dovecot does I don't see this happening. Probably too quick (or perhaps you haven't configured dotlocking). Qpopper locks the INBOX when it creates a drop copy: this can be a time consuming operation, during which you can see the .$user.pop lock file. Dovecot is more intelligent: it doesn't create copies, and goes out of its way to avoid grautitous I/O. Most of the operations can be done by consulting the indices. However, I did contrive a situation to observe lock files being created. 1) Create large INBOX file test user (assuming mbox /inbox/testuser) 2a) In one window, run a shell loop monitor while : ; do ls -al /inbox/testuser.lock done 2b) In another window, create a POP3 session and do an operation that would require a lock: telnet pop-server 110 USER testuser PASS testpassword DELE 1 ... this still won't need locking -- not until ... QUIT If you use maildir format, it may still be too quick to catch. in this situation, you can process trace the pop3 worker process to verify a lock file is created. > Is this .pop file a lock file or just a temporary file? Temporary. If you have them lying around, qpopper crashed. Note: dovecot makes lockfiles of the form "$user.lock". > If its a temp file does dovecot do the same thing elsewhere? I'm > concerned dovecot is not locking properly and there will be mailbox > corruption, so I'm trying to get dovecot to mimic what qpopper does as > much as possible. By "mimic" you mean that locking works, but otherwise, you don't want dovecot to mimic qpopper: the former is much better. I have not had problems with users complaining about scrambled files. As I said, process trace your pop3 worker process if you need to verify the locking process. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] sieve vacation question
by Andreas Schulze 10 Sep '13

10 Sep '13

Hello Stephan, I love to use the vacation extension to build an echo service. I have not to worry about whether to answer or not if the sender is a list, postmaster, mailer-daemon or other crasy thing. But i like to echo the *complete headers* back. I did not found a solution with sieve yet. Is it really impossible? Thanks Andreas

2 2

[Dovecot] Is this odd?
by LuKreme 09 Sep '13

09 Sep '13

$ doveadm user kremels field value uid 1033 gid 1033 home /home/kremels mail maildir:~/Maildir system_groups_user kreme $ doveadm user user(a)virtual.example.com field value uid 89 gid 89 home /usr/local/virtual/user(a)virtual.example.com/ mail /usr/local/virtual/user(a)virtual.example.com mail_location /usr/local/virtual/user(a)virtual.example.com The local users doesn't have a mail_location set at all, and has a very different mail definition. This seem to be a side-effect of the fact that the home of the virtual user is the top level maildir, but should I set mail to maildir:~ ?? -- Where there is a party, everyone is there Everyone will leave at exactly the same time When this party is over it will start again But not been any different be exactly the same

2 2

[Dovecot] Is dovecot locking properly?
by Scott Galambos 09 Sep '13

09 Sep '13

Hello, I'm attempting to move form qpopper 4.1 to Dovecot 2.2.5 on Linux. When a user checks POP mail qpopper seems to make a .username.pop temporary file in the same /var/mail directory as the mbox INBOX file. Watching what dovecot does I don't see this happening. Is this .pop file a lock file or just a temporary file? If its a temp file does dovecot do the same thing elsewhere? I'm concerned dovecot is not locking properly and there will be mailbox corruption, so I'm trying to get dovecot to mimic what qpopper does as much as possible. I'm using procmail and its Locking strategies are: dotlocking, fcntl(), lockf(), flock(). I'm using sendmail too. I left dovecot's locking as the defaults. Thanks for any tips.

1 0

Re: [Dovecot] More fine-grained connection limitations?
by Joseph Tam 09 Sep '13

09 Sep '13

> There is the mail_max_userip_connections setting, which helps for > dealing with number of connections at any given time, but I'm looking > for something that will help deal with users who configure their mail > clients to connect too frequently. > > ... > > It would be really great if there were a way to tarpit those users to > slow them down, or send them an imap message saying they are connecting > to often and connections have been disabled for the next 5 minutes or > something. There might be an unintended consequence: I see connection spikes when users try to do a global string search across mailboxes. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] best practice to have sent mail folder on dovecot imap server
by Thomas Koch 08 Sep '13

08 Sep '13

I've already asked this here: http://serverfault.com/questions/533940/best-practice-to-have-sent-mail- folder-on-dovecot-imap-server Hi, when I add a mail account to KMail (or most other MUA I suppose) the sent mail folder is on the local machine and I don't have my sent mails on other machines. I'd like to have a sent mail folder in IMAP and I thought that there would already exist a standard or best practice how to set this up so that the mail is only transfered once to the MTA and from the MTA to the IMAP server. I even thought to remember an RFC related to this problem? It isn't that simple, is it? I'm using Exim. Regards, Thomas Koch

3 2

[Dovecot] More fine-grained connection limitations?
by Micah Anderson 07 Sep '13

07 Sep '13

There is the mail_max_userip_connections setting, which helps for dealing with number of connections at any given time, but I'm looking for something that will help deal with users who configure their mail clients to connect too frequently. For example, I've seen users who configured their clients to check (IMAP) mail every 3 seconds. This is far too frequent and puts unnecessary load on the server. Even once per minute seems excessive to me. It would be really great if there were a way to tarpit those users to slow them down, or send them an imap message saying they are connecting to often and connections have been disabled for the next 5 minutes or something. Micah ps - what happens to a user when they hit mail_mx_userip_connections? Further connections are just denied, or dropped?

1 0

[Dovecot] Plus addressing
by LuKreme 07 Sep '13

07 Sep '13

It appease that I can enable +address filtering into separate mailboxes by simply setting $recipient_delimiter = '+'; However, is there anyway to get great control over that? For example, on one account I have a lot of +addresses I use. A few, I sort into mailboxes (like my bank, credit cards, etc). The rest are either on the “spammer => /dev/null” list or get sorted into a mailbox named “Misc” (like various newsletters and offers and sales from companies I do business with). -- Sigs are b0rk3d.

6 6

[Dovecot] Dovecot 2.1.7 not starting properly, mail not delivered
by Aldo & Caroline 07 Sep '13

07 Sep '13

On my debian box dovecot does not start properly any more, and mails don't get delivered or sent. I've googled around without finding any useful leads. Hopefully someone is willing to educate me. My guess is it must be a config problem after an upgrade, since I didn't change anything myself directly. Not sure when it started, since I this mail server is not our default machine (yet). Symptoms Upon /etc/init.d/dovecot restart my command line says [ ok ] Restarting IMAP/POP3 mail server: dovecot. But I find in /var/log/mail.log: Sep 6 11:17:36 debian2 dovecot: master: Warning: Killed with signal 15 (by pid=19112 uid=0 code=kill) Sep 6 11:17:36 debian2 dovecot: master: Dovecot v2.1.7 starting up (core dumps disabled) Sep 6 11:17:37 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:38 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:39 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:40 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:41 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:42 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:43 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:44 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: tcp:127.0.0.1:10001 lookup error for "aldo(a)alcatoka.nl" Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: 57B7D3640073: sender_canonical_maps map lookup problem for aldo(a)alcatoka.nl Sep 6 11:17:45 debian2 postfix/pickup[17004]: warning: maildrop/4EA313640071: error writing 57B7D3640073: queue file write error I do NOT see a line like ... dovecot: auth-worker(default): pgsql: Connected to 127.0.0.1 (mailserver) as mentioned in this <https://workaround.org/ispmail/squeeze/setting-up-dovecot?page=1> tutorial, which I used to set up the previous Dovecot version (which worked OK). When starting Dovecot from the command line with dovecot -F -c /etc/dovecot/dovecot.conf nothing is printed (as if the process is waiting for more input), while it should at least produce some output, right? I'm running Debian 7.1 with an ext3 filesystem together with Postfix 2.9.6 on an x86 machine. CPU info: processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 6 model name : AMD Sempron(tm) 140 Processor cpu MHz : 800.000 cache size : 1024 KB As far as I can tell, Postfix is running OK. /etc/dovecot/dovecot.conf says: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.1 ext3 auth_mechanisms = plain login disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/vmail/%d/%n/Maildir mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service auth { unix_listener auth-master { group = vmail mode = 0600 user = vmail } user = root } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = uid=3000 gid=3000 home=/var/vmail/%d/%n allow_all_users=yes driver = static } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = mail_plugins = sieve postmaster_address = aldo(a)alcatoka.nl As far as I understand, there must be a process (dovecot-auth?) that takes care of translating mail adresses, taking a string at port 10001 and returning the translated string on 10002. This process does not seem to kick off when dovecot restarts. Please tell me if I'm thinking in the right direction, and - more importantly - what I need to do to get dovecot running. I will be happy to provide more test results if that helps, just tell me what you need. Regards, Aldo Verlinde

1 1

[Dovecot] which clients support SCRAM-SHA-1
by Reindl Harald 07 Sep '13

07 Sep '13

Hi running dovecot as IMAP/POP3-proxy with auth_mechanisms = CRAM-MD5 DIGEST-MD5 SCRAM-SHA-1 APOP LOGIN PLAIN which client supports currently "SCRAM-SHA-1" to test it?

1 0

Re: [Dovecot] doveadm expunge problems
by Joseph Tam 07 Sep '13

07 Sep '13

nicolasfo wrote: > doveadm search -u *(a)mydomain.fr MAILBOX Junk savedbefore 1d : don't lists > anything.. > > What am I missed ? > > Is this the good way to change file date (touch) and by this way, have > results to savedbefore command ? No. The date.saved value is (I think) stored in its indices, and is updated via IMAP operations. This value is not derived from file timestamps. You can use doveadm fetch to get the values that dovecot uses dovecot -ftab fetch -A 'mailbox date.saved' mailbox Junk If you actually use IMAP operations to move messages from INBOX to Junk, I think you'll find that date.saved reflects the correct value. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] userdb with LDAP
by Tobi 06 Sep '13

06 Sep '13

Hi list I currently having troubles to "connect" dovecot (for proxy) to an existing LDAP. If I got the dovecot wiki right only userdb is needed for a proxy setup where the proxy does not authenticate but just forward to the backend for authentication. So I setup the following in dovecot-ldap.conf.ext user_attrs = =password,=y=nopasswd,=y=proxy,mailHost=host user_filter = (&(objectClass=posixAccount)(uid=%u)) There is a field mailHost in LDAP which defines the correct backend for the user and defined userdb in auth-ldap.conf.ext userdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext } the same config again in auth-system.conf.ext The problem is that dovecot always reports back that the user is unknown. I turned on ldap debug and got the following Sep 6 13:06:10 kolab-frontend dovecot: auth: Debug: ldap(tobi.szyndler(a)datapark.li,213.196.149.1,<88FSBrXlSQDVxJUB>): pass search: base=dc=datapark,dc=li scope=subtree filter=(&(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li)) fields=mailHost Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_search Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(&(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li))" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: AND Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter_list "(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(objectClass=posixAccount)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: simple Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_simple_filter: "objectClass=posixAccount" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(uid=tobi.szyndler(a)datapark.li)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: simple Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_simple_filter: "uid=tobi.szyndler(a)datapark.li" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_build_search_req ATTRS: mailHost Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_send_initial_request Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_send_server_request Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_result ld 0x7fbc43fb4110 msgid -1 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg ld 0x7fbc43fb4110 msgid -1 (timeout 0 usec) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg continue ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Connections: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * host: 213.196.149.116 port: 389 (default) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: refcnt: 2 status: Connected Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: last used: Fri Sep 6 13:06:10 2013 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Outstanding Requests: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * msgid 4, origid 4, status InProgress Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: outstanding referrals 0, parent count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 request count 1 (abandoned 0) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Response Queue: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Empty Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 response count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList returns ld 0x7fbc43fb4110 NULL Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_int_select Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 msgid 4 message type search-result Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 0 new referrals Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: mark request completed, ld 0x7fbc43fb4110 msgid 4 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: request done: ld 0x7fbc43fb4110 msgid 4 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: res_errno: 0, res_error: <>, res_matched: <> Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_free_request (origid 4, msgid 4) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_parse_result Sep 6 13:06:10 kolab-frontend dovecot: auth: ldap(tobi.szyndler(a)datapark.li,213.196.149.1,<88FSBrXlSQDVxJUB>): unknown user Sep 6 13:06:10 kolab-frontend dovecot: auth: Debug: ldap(tobi.szyndler(a)datapark.li,213.196.149.1,<88FSBrXlSQDVxJUB>): pass search: base=dc=datapark,dc=li scope=subtree filter=(&(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li)) fields=mailHost Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_search Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(&(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li))" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: AND Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter_list "(objectClass=posixAccount)(uid=tobi.szyndler(a)datapark.li)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(objectClass=posixAccount)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: simple Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_simple_filter: "objectClass=posixAccount" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: "(uid=tobi.szyndler(a)datapark.li)" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_filter: simple Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: put_simple_filter: "uid=tobi.szyndler(a)datapark.li" Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_build_search_req ATTRS: mailHost Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_send_initial_request Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_send_server_request Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_msgfree Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_result ld 0x7fbc43fb4110 msgid -1 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg ld 0x7fbc43fb4110 msgid -1 (timeout 0 usec) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg continue ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Connections: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * host: 213.196.149.116 port: 389 (default) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: refcnt: 2 status: Connected Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: last used: Fri Sep 6 13:06:10 2013 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Outstanding Requests: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * msgid 5, origid 5, status InProgress Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: outstanding referrals 0, parent count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 request count 1 (abandoned 0) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Response Queue: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Empty Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 response count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList returns ld 0x7fbc43fb4110 NULL Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_int_select Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_result ld 0x7fbc43fb4110 msgid -1 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg ld 0x7fbc43fb4110 msgid -1 (timeout 0 usec) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg continue ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Connections: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * host: 213.196.149.116 port: 389 (default) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: refcnt: 2 status: Connected Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: last used: Fri Sep 6 13:06:10 2013 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Outstanding Requests: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * msgid 5, origid 5, status InProgress Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: outstanding referrals 0, parent count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 request count 1 (abandoned 0) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Response Queue: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Empty Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 response count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList returns ld 0x7fbc43fb4110 NULL Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_int_select Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 msgid 5 message type search-result Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: ld 0x7fbc43fb4110 0 new referrals Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: read1msg: mark request completed, ld 0x7fbc43fb4110 msgid 5 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: request done: ld 0x7fbc43fb4110 msgid 5 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: res_errno: 0, res_error: <>, res_matched: <> Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_free_request (origid 5, msgid 5) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_parse_result Sep 6 13:06:10 kolab-frontend dovecot: auth: ldap(tobi.szyndler(a)datapark.li,213.196.149.1,<88FSBrXlSQDVxJUB>): unknown user Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_msgfree Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_result ld 0x7fbc43fb4110 msgid -1 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg ld 0x7fbc43fb4110 msgid -1 (timeout 0 usec) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: wait4msg continue ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Connections: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: * host: 213.196.149.116 port: 389 (default) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: refcnt: 1 status: Connected Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: last used: Fri Sep 6 13:06:10 2013 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Outstanding Requests: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Empty Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 request count 0 (abandoned 0) Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ** ld 0x7fbc43fb4110 Response Queue: Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: Empty Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ld 0x7fbc43fb4110 response count 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList ld 0x7fbc43fb4110 msgid -1 all 0 Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_chkResponseList returns ld 0x7fbc43fb4110 NULL Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_int_select I'm pretty sure that the error is 30cm in front of the screen :-) but I really don't see the problem Any help is highly appreciated Thanks tobi

1 1

[Dovecot] doveadm expunge problems
by nicolasfo 06 Sep '13

06 Sep '13

Hello there, I'm trying to use the doveadm expunge function, but it doesn't seems to work.. I have installed a mail test server using iredmail, Dovecot and postfix using mysql for authentications. I sent a email to this server, and change the timestamp using touch. the mail boxes are as follow : /home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49/Maildir I want to delete mails that are, let's say, 1day old from the "Junk" folder. (I put the mail I changed the date in it). I run this command : doveadm -Dv expunge -u nicolas(a)mydomain.fr mailbox "Junk" savedbefore 1d The mail is still in the "Junk" folder, and I have this output : root@mail:/home/mail/vmail1# doveadm -Dv expunge -u nicolas(a)mydomain.fr mailbox "Junk" savedbefore 1d doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: undefined symbol: i_stream_create_deflate (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) doveadm(nicolas(a)mydomain.fr): Debug: Added userdb setting: plugin/master_user=nicolas(a)mydomain.fr doveadm(nicolas(a)mydomain.fr): Debug: Added userdb setting: plugin/quota_rule=*:bytes=1073741824 doveadm(nicolas(a)mydomain.fr): Debug: Effective uid=2000, gid=2000, home=/home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49/ doveadm(nicolas(a)mydomain.fr): Debug: Quota root: name=user backend=dict args=:proxy::quotadict doveadm(nicolas(a)mydomain.fr): Debug: Quota rule: root=user mailbox=* bytes=1073741824 messages=0 doveadm(nicolas(a)mydomain.fr): Debug: Quota warning: bytes=912680550 (85%) messages=0 reverse=no command=quota-warning 85 nicolas(a)mydomain.fr doveadm(nicolas(a)mydomain.fr): Debug: Quota warning: bytes=966367641 (90%) messages=0 reverse=no command=quota-warning 90 nicolas(a)mydomain.fr doveadm(nicolas(a)mydomain.fr): Debug: Quota warning: bytes=1020054732 (95%) messages=0 reverse=no command=quota-warning 95 nicolas(a)mydomain.fr doveadm(nicolas(a)mydomain.fr): Debug: dict quota: user=nicolas(a)mydomain.fr, uri=proxy::quotadict, noenforcing=0 doveadm(nicolas(a)mydomain.fr): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir://home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49//Maildir/:INDEX=//home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49//Maildir/ doveadm(nicolas(a)mydomain.fr): Debug: maildir++: root=//home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49//Maildir, index=, control=, inbox=//home/mail/vmail1/mydomain.fr/n/i/c/nicolas-2013.09.05.14.30.49//Maildir, alt= doveadm(nicolas(a)mydomain.fr): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u doveadm(nicolas(a)mydomain.fr): Debug: shared: root=/var/run/dovecot, index=, control=, inbox=, alt= I don't understand, the output seems to be OK, except loading modules at the begining, but I think there's no effect to expunge command... Anyone to help me, please ? Thnaks in advance Nicolas -- View this message in context: http://dovecot.2317879.n4.nabble.com/doveadm-expunge-problems-tp44200.html Sent from the Dovecot mailing list archive at Nabble.com.

1 1

[Dovecot] stopping dictionary attacks (pop3)
by other＠ahhyes.net 05 Sep '13

05 Sep '13

Hi Guys, I was really hoping a couple of years later this would be addressed... I'm running Dovecot 2.2.5 on FreeBSD. Is there anyway to limit the number of auth attempts allowed in a single session? The reason for this is because I have "fail2ban" setup to firewall out any IP addresses that repeatedly auth fails. The issue occurs when the connection is already in an "established" state and the attacker uses the existing session to hammer away, fail2ban becomes ineffective as dovecot appears to allow the person to attempt authentication ad infinitum. It would be nice if there was config option that would for example cause the software to close the connection after X failed attempts. I use "pf" as the firewall on FreeBSD. Unless there was some command I could have fail2ban run a command that would destroy any tcp sessions in an established state prior to adding the offending IP to the block list, that would be the only way around the problem. Ideally it would be nice for dovecot have an option to control the number of failed auth attempts. Any suggestions? Cheers, Alex.

2 3

[Dovecot] Received header only showing localhost
by Matt Devaney 05 Sep '13

05 Sep '13

Hi all, Im a new dovecot user and a first-time poster so please forgive me if this is a stupid question, or even (as I suspect it might be) not really a Dovecot question. My system is the fairly typical mix of postfix, amavis-new, and Dovecot. For some reason Ive noticed that when I look at the mail headers for delivered messages the Received header is missing the detail of any external servers that the mail went through, and additionally the tag appears twice; for example the Welcome to the dovecot mailing list email has: Received: from localhost (localhost [127.0.0.1]) by droplet.the-wyvern.net (Postfix) with ESMTP id DDDD163F73 for <myname(a)mydomain.net>; Mon, 26 Aug 2013 16:40:19 +0000 (UTC) Received: from droplet.the-wyvern.net ([127.0.0.1]) by localhost (droplet.the-wyvern.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6AFMiG0TAHUv for <myname(a)mydomain.net>; Mon, 26 Aug 2013 16:40:17 +0000 (UTC) Searching through the dovecot.markmail archive I can see this doesnt seem to be too unusual in that there are other examples where folk have posted message headers with the above format, however Im wondering if theres a good reason for it and if I can turn it off? I quite like being able to see where my mail came from :) If theres a man / wiki page to read somewhere that explains it then please feel free to tell me to RTM (.. long as you also point me in the right direction :p ) Thanks, Matt

2 4

[Dovecot] OT: z-Push
by Christian Rößner 04 Sep '13

04 Sep '13

Hi, just a short question: I have installed and configured z-Push to use BackendIMAP. On my iPhone I have created an account and I can see my mails. Also sending works. So far so good. Now the question: When I create a new folder i.e. Test under the root (/), then I get an error. And after resyncing the folder has been created not under /, but under /0/Test. Also I can not remove that folder over ActiveSync. Does somebody have z-Push fully working with Dovecot or is z-Push designed for Cyrus and only some features are working with Dovecot? So at the moment folder create/move/delete does not work here with z-Push-2.0.3 and Dovecot 2.1.9 Thanks in advance -Christian Rößner --- Bachelor of Science Informatik Erlenwiese 14, 36304 Alsfeld T: +49 6631 78823400, F: +49 6631 78823409, M: +49 176 93118939 USt-IdNr.: DE225643613, http://www.roessner-network-solutions.com

4 4

[Dovecot] Dovecot is not creating directories properly for new accounts
by Chris Lasater 04 Sep '13

04 Sep '13

Hi, I have just set up a new dovecot server with Dovecot 2.2.5. When I create a new user and try to authenticate I get the following error Sep 03 14:33:38 imap(test2): Error: user test2: Initialization failed: Initializing mail storage from mail_location setting failed: mkdir(/home/user/apps/var/mail/imap/test2/mailboxes) failed: Permission denied (euid=503(imapd) egid=503(imapd) missing +w perm: /home/user/apps/var/mail, we're not in group 502(dovecot), dir owned by 502:502 mode=0775) Sep 03 14:33:38 imap(test2): Error: Invalid user settings. Refer to server log for more information. imapd is in the dovecot group and here are the permissions [user@MB1 logs]$ ll /home/user/apps/var/ total 4 drwxrwxr-x 4 dovecot dovecot 4096 Sep 3 14:35 mail [user@MB1 logs]$ id imapd uid=503(imapd) gid=503(imapd) groups=503(imapd),500(user),502(dovecot) if I su - imapd and then run mkdir -p /home/user/apps/var/mail/imap/test2/mailboxes everything starts working and the user can log in. Isn't Dovecot supposed to be able to create these?

2 1

[Dovecot] dsync - convert plugin missing?
by Regan Yelcich 04 Sep '13

04 Sep '13

I'm looking to convert my mbox mailboxes over to Maildir. But when I try to run the dsync command: (changed with my variables) dsync -u username mirror mbox:~/mail:INBOX=/var/mail/username found on this dovecot v2.X page here: http://wiki2.dovecot.org/Migration/MailFormat I get an error that it can't find the "convert" plugin. Am I doing something wrong? Thanks.

1 0

Re: [Dovecot] Deleting messages with Mac Mail via IMAP
by Tim Schneider 04 Sep '13

04 Sep '13

The right wording (expunge) provided me with some clues. Anyway, Mac Mail does not have such a flag. It seems to be deliberately designed to do the expunge on quitting the application. Expunge can also be triggered by using cmd+shift+k with no marked messages to empty all trashes. Using this command, one can also mark a message and expunge it directly, bypassing the trash. I don't want to exclude the possiblity that this has got something to do with the IDLE system, and could be resolved by, for example, providing the right IMAP capabilities flags upon com init. Interestingly, iOS mail does delete the message in the inbox directly when moving it to trash. Thanks anyway to the contributors of this thread, I think I will have to accept this behavior, since Apple does usually not care about customer requests to resolve bugs. Mostly they declare them to be intended stupidity, even when they sell items that behave just the opposite way. Anyway, Zarafa mail server has a flag imap_expunge_on_delete. Perhaps this would be a useful feature for Dovecot to protect admins from angry customers who use well-designed Apple products. On 2013-09-03, at 20:16 , lists-dovecot <replies-lists-a1z2-dovecot(a)listmail.innovate.net> wrote: > > > ------------ Original Message ------------ >> Date: Tuesday, September 03, 2013 07:11:40 PM +0200 >> From: Tim Schneider <tim.schneider(a)portabile.net> >> To: dovecot(a)dovecot.org >> Subject: [Dovecot] Deleting messages with Mac Mail via IMAP >> >> Hello mailing list subscribers! >> >> When I delete a message in Mac Mail 6.5 (OS X 10.8.4), >> with the option to move messages to the trash set in Mac Mail >> account preferences, the message is copied to the trash, and >> markes as trashed in the cur/inbox directory on the server (STa >> flag in the file name). >> >> My horde webmail then displays this messages correctly as trashed >> in the inbox. However, I want the message to be gone from the >> inbox. >> >> Quitting Mac Mail deletes it in the inbox reliably. >> >> Is there any IMAP setting for dovecot to get move, and not copy >> and mark as trashed behavior? >>

1 0

[Dovecot] Deleting messages with Mac Mail via IMAP
by Tim Schneider 03 Sep '13

03 Sep '13

Hello mailing list subscribers! When I delete a message in Mac Mail 6.5 (OS X 10.8.4), with the option to move messages to the trash set in Mac Mail account preferences, the message is copied to the trash, and markes as trashed in the cur/inbox directory on the server (STa flag in the file name). My horde webmail then displays this messages correctly as trashed in the inbox. However, I want the message to be gone from the inbox. Quitting Mac Mail deletes it in the inbox reliably. Is there any IMAP setting for dovecot to get move, and not copy and mark as trashed behavior? Here are my dovecot settings: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 ext4 auth_mechanisms = plain login mail_location = maildir:/var/mail/vhosts/%d/%n mail_privileged_group = mail 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.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = admin(a)xxx.xxx protocols = imap pop3 lmtp sieve service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } ssl = required ssl_cert = </etc/ssl/certs/mailportabile.pem ssl_key = </etc/ssl/private/mailportabile.key submission_host = localhost userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } protocol lda { mail_plugins = " sieve" }

3 2

Re: [Dovecot] Logging passwords on auth failure/dealing with botnets
by Joseph Tam 03 Sep '13

03 Sep '13

Michael Smith writes: > We're already running fail2ban, but it doesn't seem that effective > against botnets, when they only do one attempt per IP. Yeah, distributed BFDs are tough to block unless you can characterize the clients well. > That leaves us back to getting dovecot to log the tried password for > unknown users. Another tactic might be to hook in a authentication script: http://wiki2.dovecot.org/AuthDatabase/CheckPassword You can run this as an external plugin and won't have to muck into the dovecot innards. From here, you can log attempts, keep track of bad IPs, or take action if you spot a username/password combination that merits instant blacklisting. Joseph Tam <jtam.home(a)gmail.com>

5 10