search for: konflikte

Hi, I have finally managed to implement the Sieve "foreverypart" and "mime" extensions (RFC 5703). These are now included in the main Mercurial repository and will be included in the next release. I will be fixing a few minor details in the coming week; e.g., interaction with "include" and "editheader" extensions needs more work. Still, in the mean time,

I ran into a problem installing R 3.5 on Ubuntu Bionic Beaver. In file /etc/apt/sources.list I added the repository entry "deb https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/". But "apt-get update" now produces an error message: W: Konflikt bei Distribution: https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/ InRelease (bionic-cran35/ erwartet, aber

I have this too on Ubuntu Bionic. The English error message is: W: Conflicting distribution: https://cran.rstudio.com/bin/linux/ubuntu bionic-cran35/ InRelease (expected bionic-cran35/ but got bionic) Though the error doesn't seem to prevent use of the repository. I could apt-get install R 3.5 no problem. On Wed, Jun 13, 2018 at 2:04 PM, Ulrich Leuchtmann < ulrich.leuchtmann at

I know this is a tad tangential to dovecot, but maybe someone has some pointers for me. I'm trying to forward emails using the sieve filtering and redirect doesn't do it because it doesn't wrap the message in a new email, instead, it seems to just change the envelope From (and To). This causes the outbound relay to reject the message for security/spam reasons (forged From). It

Hello, i do some tests with sieve editheader extensions. deleteheader and addheader are working, but i noticed that new headerlines are always prepended to current header. So new lines can be found always on top. I am looking for a possibility to edit a headerline in place, without moving the new line to top of stack(replaceheader?). It is not looking good if a Subject-Line suddenly moves to

Say someone has setup spf for his domain and sends an email to a user that has in roundcube enabled the sieve forward. If the message is forwarded without altering the message headers, this could result in a message being blocked or not relayed, because sending hosts ip, is not in the spf of the from: domain. Possible solutions are: - add option if enabled, it replaces the From: with that

Hi, we are using SAMBA 3.6.1-1 (updating this archlinux machine is tooo ugly) and 3.6.6-1 on archlinux with the LDAP (Server version is 2.4.26-3) backend and manage the users, groups and computer by using the smbldap-tools. Currently we are experiencing the following problems: 1. changing the passwords takes longer than 30 seconds <- That's bad because we are using a gigabit ethernet