{"id":397,"date":"2018-03-27T12:10:09","date_gmt":"2018-03-27T11:10:09","guid":{"rendered":"http:\/\/geisti.de\/wordpress\/?p=397"},"modified":"2018-03-27T12:10:09","modified_gmt":"2018-03-27T11:10:09","slug":"sieve-mit-abweichendem-ca","status":"publish","type":"post","link":"https:\/\/geisti.de\/index.php\/2018\/03\/27\/sieve-mit-abweichendem-ca\/","title":{"rendered":"Sieve mit abweichendem CA"},"content":{"rendered":"<p>Roundcube wollte keine Verbindung mehr mit dem Sieve-Management herstellen lassen, da ich nicht bereit war zus\u00e4tzlich f\u00fcr Wildcard zu zahlen.<br \/>\nFolgender Workaround hat das Problem behoben:<\/p>\n<p>roundcube: PHP Warning: stream_socket_enable_crypto(): Peer certificate CN=`xyz.de&#8216; did not match expected CN=`mail.xyz.de&#8216; in \/usr\/share\/php\/Net\/Sieve.php on line 1180<br \/>\nroundcube: ERROR: Failed to establish TLS connection (2)<\/p>\n<p>L\u00f6sung (\/var\/lib\/roundcube\/plugins\/managesieve\/config.inc.php) :<br \/>\n\/\/ $config[&#8218;managesieve_conn_options&#8216;] = null;<\/p>\n<p>\/\/ Connection scket context options<br \/>\n\/\/ See http:\/\/php.net\/manual\/en\/context.ssl.php<br \/>\n\/\/ The example below enables server certificate validation<br \/>\n$config[&#8218;managesieve_conn_options&#8216;] = array(<br \/>\n&#8217;ssl&#8216; =&gt; array(<br \/>\n&#8218;verify_peer&#8216; =&gt; false,<br \/>\n<span style=\"color: #ff0000;\">&#8218;verify_peer_name&#8216; =&gt; false,<\/span><br \/>\n&#8218;verify_depth&#8216; =&gt; 3,<br \/>\n&#8218;cafile&#8216; =&gt; &#8218;\/etc\/openssl\/certs\/ca.crt&#8216;,<br \/>\n),<br \/>\n);<\/p>\n<p>Der Eintrag &#8222;verify_peer_name&#8220; ist in der Beispielconfig nicht vorhanden, kann aber hinzugef\u00fcgt werden, da der Parameter in der entsprechenden Funktion akzeptiert wird und vorhanden ist.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Roundcube wollte keine Verbindung mehr mit dem Sieve-Management herstellen lassen, da ich nicht bereit war zus\u00e4tzlich f\u00fcr Wildcard zu zahlen. Folgender Workaround hat das Problem behoben: roundcube: PHP Warning: stream_socket_enable_crypto(): Peer certificate CN=`xyz.de&#8216; did not match expected CN=`mail.xyz.de&#8216; in \/usr\/share\/php\/Net\/Sieve.php on line 1180 roundcube: ERROR: Failed to establish TLS connection (2) L\u00f6sung (\/var\/lib\/roundcube\/plugins\/managesieve\/config.inc.php) : \/\/\u2026 <span class=\"read-more\"><a href=\"https:\/\/geisti.de\/index.php\/2018\/03\/27\/sieve-mit-abweichendem-ca\/\">Weiterlesen &raquo;<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-397","post","type-post","status-publish","format-standard","hentry","category-computergedingens"],"_links":{"self":[{"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/posts\/397","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/comments?post=397"}],"version-history":[{"count":0,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/posts\/397\/revisions"}],"wp:attachment":[{"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/media?parent=397"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/categories?post=397"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/tags?post=397"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}