- dovecot - dovecot.org

Pipe to PHP script using Sieve Extprograms
by Thomas 21 Apr '17

21 Apr '17

Hello, I seem to be having some issues trying to setup a pipe to PHP scripts using Sieve Extprograms. I am trying to allow each individual mailbox to setup its own PHP pipe rules (in other words, each user should be able to pipe incoming emails to a user defined PHP script). I have the following lines in my main Sieve configuration file (/etc/dovecot/conf.d/90-sieve.conf): sieve_extensions = +vnd.dovecot.pipe sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_plugins = sieve_extprograms I have configured a Sieve service that looks like this (/etc/dovecot/conf.d/90-sieve-extprograms.conf): service php { # Define the executed script as parameter to the sieve service executable = /var/run/dovecot/sieve-pipe/php.sh # Use some unprivileged user for executing the program user = dovenull # The unix socket located in the sieve_pipe_socket_dir (as defined in the # plugin {} section above) unix_listener sieve-pipe/php { # LDA/LMTP must have access user = vmail mode = 0600 } } Contents of /var/run/dovecot/sieve-pipe/php.sh: #!/usr/bin/php Sieve script for one of my mailboxes: require ["fileinto", "regex", "date", "relational", "vacation"]; require ["mailbox", "imap4flags", "vnd.dovecot.pipe"]; # Move spam to spam folder if header :contains "X-Spam-Flag" "YES" { fileinto "Junk"; # Stop here so that we do not reply on spams stop; } pipe :try "php /var/www/web2/piping.php support(a)example.com" keep; This results however in the following error in my log file: main script: line 5: error: require command: unknown Sieve capability `vnd.dovecot.pipe'. main script: line 14: error: unknown command 'pipe' (only reported once at first occurence). main script: error: validation failed. I am also not quite confident I have set this up correctly. Am I heading in the right direction for what I am trying to achieve? Dovecot version: 2.2.10 dovecot -n: # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.16.1.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) auth_mechanisms = plain login disable_plaintext_auth = no listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_plugins = " quota" mail_privileged_group = 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 passdb { args = /etc/dovecot-sql.conf driver = sql } plugin { quota = dict:user::file:/var/vmail/%d/%n/.quotausage sieve = /var/vmail/%d/%n/.sieve } protocols = imap pop3 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 } user = root } service imap-login { client_limit = 1000 process_limit = 500 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/postfix/smtpd.cert ssl_key = </etc/postfix/smtpd.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /etc/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota postmaster_address = root@localhost } protocol lmtp { mail_plugins = quota sieve postmaster_address = webmaster@localhost }

2 2

namespace assertion failed
by Elisamuel Resto 21 Apr '17

21 Apr '17

Hello, I'm trying to figure out if this is a configuration issue or an actual bug. Dovecot does start, but if anybody tries to log in or if you run sievec you get an assertion fail and a coredump. --- sievec(root): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) sievec(root): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9c3a2) [0x7ff70e2133a2] -> /usr/lib/dovecot/libdovecot.so.0(+0x9c429) [0x7ff70e213429] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff70e1a5e41] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find+0xc8) [0x7ff70e4e03a8] -> /usr/lib/dovecot/modules/lib11_trash_plugin.so(+0x1e56) [0x7ff70d5ace56] -> /usr/lib/dovecot/libdovecot-storage.so.0(hook_mail_user_created+0x1eb) [0x7ff70e4ecfeb] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_user_init+0x206) [0x7ff70e4f1fb6] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_next+0x438) [0x7ff70e4f00c8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_lookup_next+0x4c) [0x7ff70e4f068c] -> sievec(sieve_tool_init_finish+0xc1) [0x403371] -> sievec(main+0xd2) [0x402cb2] -> /usr/lib/libc.so.6(__libc_start_main+0xf1) [0x7ff70ddf3511] -> sievec(_start+0x2a) [0x402f3a] Aborted (core dumped) --- Coredump as follows: --- #0 0x00007ff70de06a10 in raise () from /usr/lib/libc.so.6 #1 0x00007ff70de0813a in abort () from /usr/lib/libc.so.6 #2 0x00007ff70e21339a in ?? () from /usr/lib/dovecot/libdovecot.so.0 #3 0x00007ff70e213429 in default_fatal_handler () from /usr/lib/dovecot/libdovecot.so.0 #4 0x00007ff70e1a5e41 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 #5 0x00007ff70e4e03a8 in mail_namespace_find () from /usr/lib/dovecot/libdovecot-storage.so.0 #6 0x00007ff70d5ace56 in ?? () from /usr/lib/dovecot/modules/lib11_trash_plugin.so #7 0x00007ff70e4ecfeb in hook_mail_user_created () from /usr/lib/dovecot/libdovecot-storage.so.0 #8 0x00007ff70e4f1fb6 in mail_user_init () from /usr/lib/dovecot/libdovecot-storage.so.0 #9 0x00007ff70e4f00c8 in mail_storage_service_next () from /usr/lib/dovecot/libdovecot-storage.so.0 #10 0x00007ff70e4f068c in mail_storage_service_lookup_next () from /usr/lib/dovecot/libdovecot-storage.so.0 #11 0x0000000000403371 in sieve_tool_init_finish () #12 0x0000000000402cb2 in main () --- Any help appreciated! -Sam

3 3

[BUG] config-parser.c: line 89 - crash on comma in namespace mailbox
by Alek 21 Apr '17

21 Apr '17

Hi! On the latest versions (2.2.28, 2.2.29.x) we get crash on dovecot config parse. Error in config parser when checking namespace mailbox name. Reason: comma in mailbox name. Worked well in versions < 2.2.22. Do not know if it was working on 2.2.23-2.2.27, skipped this versions. Example: namespace inbox { mailbox "&BB4EQgQ,BEAEMAQyBDsENQQ9BD0ESwQ1-" { special_use = \Sent } } Error: # dovecot -n # 2.2.29.1 (e0b76e3): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) doveconf: Panic: file config-parser.c: line 89 (config_add_type): assertion failed: (ret > 0) doveconf: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9b89a) [0x7fa1f8cc789a] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7fa1f8cc81d2] -> /usr/lib64/dovecot/libdovecot.so.0(+0x2f81a) [0x7fa1f8c5b81a] -> /usr/bin/doveconf() [0x40b213] -> /usr/bin/doveconf(config_parser_apply_line+0x763) [0x40b983] -> /usr/bin/doveconf(config_parse_file+0x821) [0x40c351] -> /usr/bin/doveconf(main+0x255) [0x406845] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7fa1f88b6d1d] -> /usr/bin/doveconf() [0x4051f9] doveconf: Error: managesieve-login: dump-capability process killed with signal 6 doveconf: Panic: file config-parser.c: line 89 (config_add_type): assertion failed: (ret > 0) doveconf: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9b89a) [0x7f6dfa20489a] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7f6dfa2051d2] -> /usr/lib64/dovecot/libdovecot.so.0(+0x2f81a) [0x7f6dfa19881a] -> /usr/bin/doveconf() [0x40b213] -> /usr/bin/doveconf(config_parser_apply_line+0x763) [0x40b983] -> /usr/bin/doveconf(config_parse_file+0x821) [0x40c351] -> /usr/bin/doveconf(main+0x255) [0x406845] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f6df9df3d1d] -> /usr/bin/doveconf() [0x4051f9] Info: &BB4EQgQ,BEAEMAQyBDsENQQ9BD0ESwQ1- - is a valid mailbox name for russian Outlook folder "Отправленные".

2 1

LDAP schema ?
by Dave Dodd 21 Apr '17

21 Apr '17

Hi, I am trying to determine the correct LDAP schema I need to use to have either mailLocation or mailboxPath available ? Should I be just adding this to one of my own custom objectClasses ? -- Dave

4 5

javamail imap listing
by Matthew Broadhead 20 Apr '17

20 Apr '17

Hi, i am using dovecot-2.2.10-7.el7.x86_64 on centos-release-7-3.1611.el7.centos.x86_64. if i follow this tutorial https://delog.wordpress.com/2011/05/10/access-imap-server-from-the-command-… i can login to my server and successfully list the folders using tag LIST "" "*" * LIST (\HasNoChildren) "." INBOX tag OK List completed. no folders are listed using tag LIST / "*" tag OK List completed. when i request a folder listing using JavaMail it similarly sends the following command and no folders are listed a97 LIST / "*" a97 OK List completed. if i follow the tutorial again and use my gmail account instead of my dovecot installation i can successfully list folders using both methods tag LIST / "*" * LIST (\HasNoChildren) "/" "youtube" tag OK List completed. is there some way to make dovecot list folders when it receives the command LIST / "*" i note that in the listings my dovecot installation has "." in the middle and gmail has a "/"

3 5

JavaMail setFlags on readonly folder
by Gabriele Bulfon 20 Apr '17

20 Apr '17

Hi, I'm facing a strange issue using JavaMail, where Dovecot let me open "READ_WRITE" a folder with readonly ACLs (same happens on other imap servers), but then doesn't issue any error when if try to setFlags(...) on that folder. The result is that the code thinks the folder marked the messages (deleted, flagged, etc), while it actually did not. Just refreshing the folder from the java client, you get back your original messages as they were before the operation. Is there any known issue about this? Gabriele ---------------------------------------------------------------------------------------- Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon

2 1

Dovecot not listening when testing connection
by Alvaro Lacerda 20 Apr '17

20 Apr '17

Hi, This is my environment: SMTP: Exim 4.89 with Mailscanner 5.0.3 IMAP: Dovecot 2.2.10 At the moment I'm just trying to test out my Dovecot to check if it's listening on port 993. *netstat -tuln:* Shows that my machine is listening on ports 143 and 993. *telnet localhost 993: *This is my issue, I get the following message: # telnet localhost 993 Trying ::1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. According to the wiki.dovecot test installation page I should be getting this instead: https://wiki.dovecot.org/TestInstallation Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. When I run doveconf this is what I get: # doveconf protocols listen protocols = imap pop3 lmtp listen = *, :: Does anyone have an idea of what I'm missing here? Thanks. -- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete this material from any computer. Cantella does not permit execution of trades requested by email. Please call to ensure prompt execution of orders, as we are not responsible for orders transmitted through email. Investing involves risk and you may incur a profit or a loss. Please carefully consider investment objectives, risks, charges, and expenses before investing. Cantella & Co., Inc. does not provide legal or tax advice. For legal or tax advice, please seek the services of a qualified professional. The performance data featured represents past performance, which is no guarantee of future results. Mutual funds and UITs are sold by prospectus only. Please carefully consider the fund's investment objective, risks, charges and expenses applicable to a continued investment in the fund before investing. For this and other information, call or write for a free prospectus, or view one online. Read it carefully before you invest or send money. Fixed income is subject to availability and change in price. Bonds are subject to market and interest rate risk if sold prior to maturity. Interest rate increases can cause the price of a debt security to decrease. Interest income may be subject to federal, state, local, and/or alternative minimum tax. In accordance with industry regulations, all messages are retained and are subject to monitoring. This message has been scanned for viruses and dangerous content and is believed to be clean. Securities offered through Cantella & Co., Inc., Member FINRA/SIPC. Home Office: 28 State St 40th Floor, Boston, MA 02109 Telephone: (800)652-8358

3 8

Using filter in an imapsieve script?
by Tobi 20 Apr '17

20 Apr '17

Hello list I currently have an issue with an imapsieve script on my dovecot server CentOS Linux release 7.3.1611 (Core) Dovecot 2.2.26.0 (23d1de6) Pigeonhole 2.2.26.0 The goal is to "fire" an imapsieve script upon mailclient saves message to sent folder I setup the following in 90-plugin.conf: plugin { sieve_plugins = sieve_imapsieve sieve_extprograms sieve_extensions = +vnd.dovecot.filter +vnd.dovecot.pipe +vnd.dovecot.execute sieve_filter_bin_dir = /etc/dovecot/sieve-filters sieve_pipe_bin_dir = /etc/dovecot/sieve-filters sieve_execute_bin_dir = /etc/dovecot/sieve-filters sieve_filter_exec_timeout = 10000 sieve_pipe_exec_timeout = 10000 sieve_execute_exec_timeout = 10000 imapsieve_mailbox1_name = Sent imapsieve_mailbox1_causes = COPY APPEND imapsieve_mailbox1_before = file:/home/vmail/domain/user/dovecot-crypt-sent.sieve } and the content of the sieve script is: require ["environment", "vnd.dovecot.filter", "variables", "imapsieve", "vnd.dovecot.pipe", "vnd.dovecot.execute"]; if anyof (environment :is "imap.cause" "APPEND", environment :is "imap.cause" "COPY") { filter "gpgit" "myuser(a)mydomain.tld"; } gpgit is a perl script that encrypts a given message using the users pub key and returns back the encrypted message As a sieve script for lmtp/lda it works fine and encrypted messages show up in the mailbox. But it does not work if it is used as imap sieve script There is nothing in the logs that indicates a problem with the imap sieve script. Is it possible that 'filter' is not supported for imapsieve as it changes the content of a message? Thanks for any hint tobi

2 6

RSA key not found
by Michael Segel 20 Apr '17

20 Apr '17

I’ve got a couple of issues with a new mail server set up… I’m getting the following error: warning: cannot get RSA certificate from file /etc/pki/dovecot/certs/<mycert>.pem: disabling TLS support The problem is that <mycert>.pem isn’t an RSA ticket, but a X509 certificate. The RSA ticket is in /etc/pki/dovecot/private directory. I checked both files and they are good certificates. I’m using webmin to manage my server. In webmin, the TLS certificate file is the X509 and the private key is the RSA file. So why does Postfix check the certificate link for the RSA file and not the X509? Thx -Mike

2 1

Adding secure POP3?
by ＠lbutlr 20 Apr '17

20 Apr '17

I have a working server that only allows connections over secure IMAP (port 993) and secured submission (587). However, I have one account that has been forwarding mail to gmail for many years and that is getting to be more and more of a problem as more large sites enforce DMARC. So, the only way that gmail will pull mail is via pop3, so I need to add pop3 access. 1) How do I add a secure (TLS) POP3 service to dovecot 2) can I restrict access to that to specific users? Domains? OT, but someone probably knows, is secured POP3 going to work with gmail? ===BEGIN passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service imap-login { inet_listener imaps { port = 993 ssl = yes } } ===END I did read <https://wiki.dovecot.org/SSL/DovecotConfiguration> but it’s about adding ssl to an existing setup. -- Apple broke AppleScripting signatures in Mail.app, so no random signatures.

3 5