- dovecot - dovecot.org

"error: number of redirect actions exceeds policy limit"
by Kai Sommer 27 Jan '15

27 Jan '15

Greetings, after testing a lot with my system I have to write to this list to ask for help from the cummunity. My system: * Ubuntu 12.04.5 LTS * Dovecot 2.0.19 * Dovecot config (extract) ––––– 8< ––––– plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_max_redirects = 10 } ––––– >8–––––– * Sieve filter rules ––––– 8< ––––– require ["copy"]; # rule:[Alles weiterleiten] if true { redirect "mail_1@mydomain"; redirect "mail_2@mydomain"; redirect "mail_3@mydomain"; redirect "mail_4@mydomain"; redirect "mail_5@mydomain"; redirect "mail_6@mydomain"; keep; stop; } ––––– >8–––––– Problem scenario: With the redirect-filter (see above) Dovecot redirects a incoming email to the first address and stops withe the message "error: number of redirect actions exceeds policy limit" (.dovecot.sieve.log). In my mail.log I see the message "Error: sieve: execution of script $PATH/.dovecot.sieve failed, but implicit keep was successful (user logfile $PATH/.dovecot.sieve.log may reveal additional details)". If I reduce the count of recipients to four – which is the Dovecot default number – everything will redireced as expected. I only could find an old problem report here [0] where as the posted solution doesn't work for me (as you can see above). (Also I tried the rule "redirect :copy" that doesn't changed something …) [0] <http://dovecot.org/pipermail/dovecot/2012-August/085038.html> → Is this problem known? – Is there a solution for that problem? Thanks a lot and best regards! – Kai -- Kai Sommer sig: 5E2E FA58 43BD 5599 4068 | pubkey: http://ma.ximi.se/mekey

2 1

Thunderbird: improper command pipelining after EHLO
by Leander Schäfer 27 Jan '15

27 Jan '15

I couldn't find working solutions for this anomalie on the net. What does this mean and does someone know how to fix this? postfix/smtpd[18757]: improper command pipelining after EHLO from unknown[192.168.10.233]: QUIT\r\n Thanks Best Regards, Leander

4 4

imap-login: Fatal: pipe() failed: Too many open files
by Leander Schäfer 26 Jan '15

26 Jan '15

Hi I keep on getting errors and can't connect/login to Dovecot. I did my research but unfortunately without success. It is for sure not ulimit because ulimit is set to unlimited per default already. Still , it complains about "Too many open files" but this is a test system and the service dovecot and postfix have just been started. No one except me is testing on this system. This is very weired ;/ root@WM-01 [~]$ service dovecot stop; service postfix stop ; echo "" > /var/log/maillog ; echo "" > /var/log/slapd.log ; service postfix start ; service dovecot start Stopping dovecot. Waiting for PIDS: 3245. postfix/postfix-script: stopping the Postfix mail system postfix/postfix-script: starting the Postfix mail system Starting dovecot. root@WM-01 [~]$ telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. root@WM-01 [~]$ cat /var/log/mail Jan 26 01:39:12 WM-01 dovecot: imap-login: Fatal: pipe() failed: Too many open files Jan 26 01:39:12 WM-01 dovecot: master: Error: service(imap-login): command startup failed, throttling for 4 secs If I uncoment port = 0 in POP and IMAP then it looks even worse then above. Telnet is not even closed by remote host and three of the "Too many open files" errors are showing up in maillog: root@WM-01 [~]$ telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. ^] telnet> Connection closed. root@WM-01 [~]$ cat /var/log/maillog Jan 26 01:45:19 WM-01 postfix/postfix-script[60560]: starting the Postfix mail system Jan 26 01:45:19 WM-01 postfix/master[60562]: daemon started -- version 1.0, configuration /usr/local/etc/postfix Jan 26 01:45:19 WM-01 dovecot: master: Dovecot v2.2.15 starting up for imap, pop3, lmtp Jan 26 01:45:24 WM-01 dovecot: imap-login: Error: socket(login) failed: Too many open files Jan 26 01:45:24 WM-01 dovecot: imap-login: Error: auth: connect(login) failed: Too many open files Jan 26 01:45:24 WM-01 dovecot: imap-login: Error: net_accept() failed: Too many open files root@WM-01 [~]$ Does anyone have an idea what could be wrong here? I attached the relevant configuration below. I use OpenLDAP as backend. Please let me know if you need more information. Thank you very much. Best Regards, Leander # ========================== dovecot -n ============================== # # 2.2.15: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.6 (3e924b1b6c5c+) # OS: FreeBSD 10.1-RELEASE amd64 ufs auth_debug = yes auth_debug_passwords = yes auth_failure_delay = 3 secs auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_greeting = Welcome to Mail Server. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_debug = yes mail_gid = vmail mail_location = maildir:/var/mail/%d/%n mail_plugins = quota expire mail_log notify mail_privileged_group = mail mail_temp_dir = /tmp/Dovecot 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 duplicate 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/dovecot-ldap.conf.ext driver = ldap } plugin { expire = Trash mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = maildir:User quota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_rule = *:storage=1G quota_rule2 = Trash:storage=+30%% quota_rule3 = Sent:storage=+30%% quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh postmaster_address = info(a)netocean.de sendmail_path = /usr/local/sbin/sendmail service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imaps { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } service pop3-login { inet_listener pop3s { port = 0 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = required ssl_cert = </etc/ssl/RootCA/certs/192.168.50.101.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ECDSA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA ssl_key = </etc/ssl/RootCA/certs/192.168.50.101.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_ssl = yes protocol lda { mail_plugins = sieve } protocol imap { mail_max_userip_connections = 3 mail_plugins = imap_quota imap_zlib } protocol pop3 { mail_max_userip_connections = 3 } # ======================== dovecot/conf.d/auth-ldap.conf.ext =================== # passdb { driver = ldap # Path for LDAP configuration file, see example-config/dovecot-ldap.conf.ext args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext } # "prefetch" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # <doc/wiki/UserDatabase.Prefetch.txt> userdb { driver = prefetch } userdb { driver = ldap args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext # Default fields can be used to specify defaults that LDAP may override #default_fields = home=/home/virtual/%u } # ======================== dovecot/dovecot-ldap.conf.ext =================== # hosts = 127.0.0.1:389 dn = uid=dovecot,ou=systemuser,ou=mail,dc=MyDomain,dc=TLD dnpass = TopSecret tls = yes tls_cert_file = /etc/ssl/RootCA/certs/192.168.50.101.pem tls_key_file = /etc/ssl/RootCA/certs/192.168.50.101.key debug_level = -1 auth_bind = yes ldap_version = 3 base = ou=accounts,ou=mail,dc=MyDomain,dc=TLD scope = subtree user_attrs = mailStorageDirectory=home, mailUidNumber=uid, mailGidNumber=gid, mailQuotaSize=quota_rule=*:bytes=%$, mailQuotaCount=quota_rule2 user_filter = (&(objectClass=mailAccount)(mailAddress=%u)) pass_attrs = mailAddress=user,mailPassword=password pass_filter = (&(objectClass=mailAccount)(mailAccountStatus=active)(mailAddress=%u)) default_pass_scheme = SSHA

3 8

Re: LDA input validation
by Joseph Tam 26 Jan '15

26 Jan '15

St?phane Cottin writes: >> You're stilling going to lose contents. If dspam fails, the mail >> is dumped, the LDA returns exit code 75, and the MTA will probably >> issue a bounce Email to the sender. > > from dovecot-lda man page : > > 75 A temporary failure. This is returned for almost all failures. See the log file for > details. (EX_TEMPFAIL) > > The mta keep the mail and retry delivery later, which is what I need. Ah, my mistake. But ... > I don't want to deliver email on dspam error, I prefer TEMPFAIL and > future retries, so I have a chance to fix the issue later without > loosing or deliver unprocessed mails ... you only have a limited time to fix it. Depending on the sending MTA's retry schedule, you might have only a few days or less to to deal with it before the sending MTA stops trying. If it's important not to lose mail, then the deliver on failure strategy would be more appropriate. You can even copy the input message that caused dpam to crash to an inspection queue for later perusal. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: LDA input validation
by Joseph Tam 26 Jan '15

26 Jan '15

St?phane Cottin writes: > dspam already send errors to syslog, the point here is to never loose > email contents. This was a wrong design, i'm now use a wrapper instead > ( see my previous post for details ). You're stilling going to lose contents. If dspam fails, the mail is dumped, the LDA returns exit code 75, and the MTA will probably issue a bounce Email to the sender. If you really don't want the recipient to lose Email, you should buffer the input into a file, run dspam on it, and if the output is not-null, pipe it to dovecot-lda, otherwise pipe the original input. Joseph Tam <jtam.home(a)gmail.com>

4 6

Re: sieve filter not working
by Christian Kivalo 24 Jan '15

24 Jan '15

Am 23. Jänner 2015 22:02:06 MEZ, schrieb Michael Williamson <michael.h.williamson(a)gmail.com> Hello, >> Another question: >> Local mail delivery of received mail from external sources does >indeed >> work? > >Yes. > That is good. >> If so, was that log excerpt in one of the former mails an example of >> such delivery? > >There are dovecot messages in "/var/log/maillog" showing only >imap-login & disconnected. >When I monitor "/var/log/maillog" while sending spam, there are no >messages containing 'dovecot'. I attached that output to a previous >post. It has only messages from postfix and amavis. > Ther should be messages from dovecot when receiving mail at least when dovecot lda has something to do with delivery. >home_mailbox = Maildir/ This tells postfix where to deliver the mails. dovecot is not configured to delivet mails. Take a look at dovecot wiki there are examples of how to incorporate dovecot lda into thendelivery process. >> I believe dovecot has actually nothing to do with delivering your >mails >> so no sieve filters are applied... > >Is it postfix? > yes, seems so >>> Thanks, >>> -Mike - christian

3 3

from Cyrus to Dovecot, seen status on cyrus.index files
by Norberto Bensa 24 Jan '15

24 Jan '15

Hello, Using cyrus2dovecot (https://github.com/a-schild/cyrus2dovecot) I have migrated some test mailboxes from Cyrus (2.4.17) to Dovecot (2.2.9). The problem I'm having is that the seen status is in cyrus.index files, which cyrus2dovecot doesn't understand. Does anyone use cyrus2dovecot for migrations? If so, how do you deal with seen status when it is stored in the .index files? Many thanks in advance, Norberto

4 6

Re: LDA input validation
by Joseph Tam 24 Jan '15

24 Jan '15

St?phane Cottin writes: > A typical .qmail file : > > | /usr/bin/dspam --client --deliver=stdout --user "$EXT@$USER" | /usr/bin/preline -f /usr/lib/dovecot/dovecot-lda -d "$EXT@$USER" -a "$EXT@$USER" -m "$EXT2" > > When dspam segfault or is killed, preline receive an empty content and > only pass to dovecot-lda two headers ( Return-Path and Delivered-To ). > Then dovecot-lda delivers successfully and the original message > contents are lost. Steffen Kaiser rightly points out: > That's the problem of the used Unix pipe and broken by design. The right > member of the pipe (preline) runs independendly of dspam and recieves no > content via pipe. Why should preline or dovecot-lda believe there is an > error? [... and suggests a wrapper script that aborts delivery on empty > dspam output.] I'm not sure if it's appropriate under your circumstances, but you can also pass stderr to stdout as well, and the recipient will get some diagnostic message, which may or may not be helpful. | /usr/bin/dspam --client --deliver=stdout --user "$EXT@$USER" 2>&1 | ... Joseph Tam <jtam.home(a)gmail.com>

2 1

LDA input validation
by Stéphane Cottin 24 Jan '15

24 Jan '15

Hi, I'm using qmail + dspam + dovecot-lda. A typical .qmail file : | /usr/bin/dspam --client --deliver=stdout --user "$EXT@$USER" | /usr/bin/preline -f /usr/lib/dovecot/dovecot-lda -d "$EXT@$USER" -a "$EXT@$USER" -m "$EXT2" When dspam segfault or is killed, preline receive an empty content and only pass to dovecot-lda two headers ( Return-Path and Delivered-To ). Then dovecot-lda delivers successfully and the original message contents are lost. Should dovecot-lda returns an error in such conditions ( invalid contents ) ? Qmail will keep it in the queue and retry delivery later. Stéphane

2 2

Mailbox corruption (dovecot 2.2.13, Debian 8)
by Santiago Vila 24 Jan '15

24 Jan '15

Hello. The attached mbox folder becomes corrupted in the server when being retrieved by fetchmail using the --folder option. This happens on a system running Debian jessie (i.e. dovecot 2.2.13) using the default configuration. I've reported this to Debian here: https://bugs.debian.org/776094 but I thought it would be good to post it here as well in case it is still a bug in the latest version (well, if it's not anymore a bug in the latest version, a patch against 2.2.13 will surely help the Debian maintainer in either case). Thanks.

1 0