search for: proasyl

...you are not the > intended recipient you are to delete this e-mail immediately, disregard > its contents and disclose them to no other persons. > > -----Original Message----- > From: Lothar Schilling via dovecot <dovecot at dovecot.org> > Reply-To: Lothar Schilling <ls at proasyl.de> > To: dovecot at dovecot.org > Subject: Character not allowed in mailbox name > Date: Mon, 22 Jul 2019 08:33:45 +0200 > > Hi everybody, > > after an update this morning to dovecot 2.3.7 we cannot connect to our > shared mailboxes anymore. The error message as issued i...

Hi everybody, after an update this morning to dovecot 2.3.7 we cannot connect to our shared mailboxes anymore. The error message as issued in Thunderbird: "Character not allowed in mailbox name '.'" I didn't change anything about the configuration. Output of dovecot -n: [...] namespace { ? list = children ? location = maildir:%%h:INDEX=%h/shared/%%u ? prefix = Shared/%%u/

...intended recipient you are to delete this e-mail immediately, disregard >> its contents and disclose them to no other persons. >> >> -----Original Message----- >> From: Lothar Schilling via dovecot <dovecot at dovecot.org> >> Reply-To: Lothar Schilling <ls at proasyl.de> >> To: dovecot at dovecot.org >> Subject: Character not allowed in mailbox name >> Date: Mon, 22 Jul 2019 08:33:45 +0200 >> >> Hi everybody, >> >> after an update this morning to dovecot 2.3.7 we cannot connect to our >> shared mailboxes anym...

Hi everybody, we have a Centos 6 host with libvirtd 0.10.2. It's holding a storage pool of about 3.5 TB with 4 VMs. I decided to rearrange them, so I destroyed and undefined two of them. But now I am not able to install a new one because virsh gives me an "not enough space left". Those two undefined VMs still linger around somehow occupying a lot of that storage. How can I get

virsh list --all 15    VM1    running 16    VM2    running ps ax | grep virt 14281 ?        Sl   1170:30  /usr/libexec/qemu-kvm -name VM1 [...] 14384 ?        Sl   376:45    /usr/libexec/qemu-kvm -name VM2 [...] Am 14.05.2020 um 17:45 schrieb Alvin Starr: > List your storage pool to insure that they have been deleted from the > pool. > If they are not there anymore then check to

Thank you, that's it! virsh vol-list storage VM1   /dev/storage/VM1.img VM2   /dev/storage/VM2.img VM3   /dev/storage/VM3.img [dead] VM4   /dev/storage/VM4.img [dead] A last stupid question (I don't want to make a big mistake ...): Is virsh vol-delete VM3 virsh vol-delete VM4 the right command to get rid of the offending ones? Am 14.05.2020 um 19:10 schrieb Alvin Starr: > >

Being a newbie to Samba 4 and OpenLDAP I am setting up a DC going exactly by the rules, testing and taking my time. I got to the point where I would switch, just testing, roles from DC1 to DC2 and vice versa. Switching all roles from DC1 to DC2 was a piece of cake, reswitching "domaindns" and "forestdns" to DC1 wasn't, though: samba-tool fsmo transfer --role=domaindns -k

Hi everybody, having set up Samba 4.12.6 as DC on Debian 10.5 "smbclient -L dc" give me this: Enter PA\root's password: Anonymous login successful ??????? Sharename?????? Type????? Comment ??????? ---------?????? ----????? ------- ??????? sysvol????????? Disk ??????? netlogon??????? Disk ??????? IPC$??????????? IPC?????? IPC Service (Samba 4.12.6-Debian) SMB1 disabled -- no

Am 11.08.2020 um 16:02 schrieb Rowland penny via samba: > On 11/08/2020 14:54, Lothar Schilling via samba wrote: >> Yep, that did it, thanks a lot, "-k yes" wasn't good enough. There now >> was another error, though: >> >> ERROR(<type 'exceptions.AttributeError'>): uncaught exception - 'module' >> object has no attribute

Yep, that did it, thanks a lot, "-k yes" wasn't good enough. There now was another error, though: ERROR(<type 'exceptions.AttributeError'>): uncaught exception - 'module' object has no attribute 'drs_utils' The solution offered and working is inserting ? import samba ? import samba.getopt as options ? import ldb +import samba.drs_utils ? from ldb

Hi everybody, I've set up an new CentOS 7.6.1810 server. Then, via yum I installed qemu-kvm libvirt libvirt-python libguestfs-tools virt-install. There were no problems. But when I try to systemctl start libvirtd I get the following message: "libvirtd: process 472: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)"

Am 02.05.2019 um 11:43 schrieb Martin Kletzander: > On Thu, May 02, 2019 at 11:22:39AM +0200, Lothar Schilling wrote: >> Hi everybody, >> >> I've set up an new CentOS 7.6.1810 server. Then, via yum I installed >> qemu-kvm libvirt libvirt-python libguestfs-tools virt-install. There >> were no problems. But when I try to >> >> systemctl start libvirtd

Am 03.05.2019 um 16:43 schrieb Martin Kletzander: > On Thu, May 02, 2019 at 02:25:28PM +0200, Martin Kletzander wrote: >> On Thu, May 02, 2019 at 01:07:32PM +0200, Michal Privoznik wrote: >>> On 5/2/19 12:08 PM, Lothar Schilling wrote: >>> >>>> I turned logging up to maximum. That's all I get: >>>> >>>> May  2 11:02:06 hl308-3