similar to: Fatal: All your namespaces have a location setting.

Displaying 20 results from an estimated 3000 matches similar to: "Fatal: All your namespaces have a location setting."

2017 Nov 06
1
mail_crypt plugin, few questions
> > On 06.11.2017 13:20, Zbyszek ???kiewski wrote: >> >>> Wiadomo?? napisana przez Aki Tuomi <aki.tuomi at dovecot.fi> w dniu 06.11.2017, o godz. 08:44: >>> >>> On 04.11.2017 20:52, Zbyszek ???kiewski wrote: >>>> Hi, >>>> >>>> I have few questions regarding mail_crypt: >>>> >>>> 1) Is
2017 Nov 06
2
mail_crypt plugin, few questions
> Wiadomo?? napisana przez Aki Tuomi <aki.tuomi at dovecot.fi> w dniu 06.11.2017, o godz. 08:44: > > On 04.11.2017 20:52, Zbyszek ???kiewski wrote: >> Hi, >> >> I have few questions regarding mail_crypt: >> >> 1) Is mail_crypt_global_private_key file read upon dovecot start/restart only or it is/can be read in any other time? I have made few tests by
2017 Nov 04
2
mail_crypt plugin, few questions
Hi, I have few questions regarding mail_crypt: 1) Is mail_crypt_global_private_key file read upon dovecot start/restart only or it is/can be read in any other time? I have made few tests by starting dovecot and removing master key for decryption - therefore it is not available on the platform - it only reside in memory, removing one of attack vectors 2) Is there planned any ?rollout? for key
2012 Mar 04
4
dsync replication available for testing
In dovecot-2.1 hg you can now test dsync-based replication. Everything isn't finished yet, but it appears to work and I've enabled it for my @dovecot.fi mails. Some issues: - public namespace isn't replicated at all - shared namespace is replicated, but not private mail flags - I've only tested SSH replication setup now, not director replication setup (and director setup
2017 Nov 06
0
mail_crypt plugin, few questions
On 06.11.2017 13:20, Zbyszek ???kiewski wrote: > >> Wiadomo?? napisana przez Aki Tuomi <aki.tuomi at dovecot.fi> w dniu 06.11.2017, o godz. 08:44: >> >> On 04.11.2017 20:52, Zbyszek ???kiewski wrote: >>> Hi, >>> >>> I have few questions regarding mail_crypt: >>> >>> 1) Is mail_crypt_global_private_key file read upon dovecot
2016 Dec 06
3
[PATCH] virtio-net: Fix DMA-from-the-stack in virtnet_set_mac_address()
With CONFIG_VMAP_STACK=y, virtnet_set_mac_address() can be passed a pointer to the stack and it will OOPS. Copy the address to the heap to prevent the crash. Cc: Michael S. Tsirkin <mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> Cc: Laura Abbott <labbott at redhat.com> Reported-by: zbyszek at in.waw.pl Signed-off-by: Andy Lutomirski <luto at kernel.org> ---
2016 Dec 06
3
[PATCH] virtio-net: Fix DMA-from-the-stack in virtnet_set_mac_address()
With CONFIG_VMAP_STACK=y, virtnet_set_mac_address() can be passed a pointer to the stack and it will OOPS. Copy the address to the heap to prevent the crash. Cc: Michael S. Tsirkin <mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> Cc: Laura Abbott <labbott at redhat.com> Reported-by: zbyszek at in.waw.pl Signed-off-by: Andy Lutomirski <luto at kernel.org> ---
2017 Nov 06
0
mail_crypt plugin, few questions
On 04.11.2017 20:52, Zbyszek ???kiewski wrote: > Hi, > > I have few questions regarding mail_crypt: > > 1) Is mail_crypt_global_private_key file read upon dovecot start/restart only or it is/can be read in any other time? I have made few tests by starting dovecot and removing master key for decryption - therefore it is not available on the platform - it only reside in memory,
2014 Mar 12
1
dovecot 2.2.9 replication
Good afternoon, I have a problem with replication is configured in Dovecot, I have two servers, they are version 2.2.9. Here is their configuration /root at mx1:/etc/dovecot# dovecot -n// //# 2.2.9: /etc/dovecot/dovecot.conf// //# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 ext4// //auth_debug = yes// //auth_debug_passwords = yes// //auth_mechanisms = plain login// //auth_socket_path =
2017 Mar 01
2
[systemd-devel] udev virtio by-path naming
On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote: > >>>> One could argue about back-level compatibility, but virtio by-path > >>>> naming has changed multiple times. We have seen virtio-pci-virtio<n> > >>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It > >>>> might be a good time now
2017 Mar 01
2
[systemd-devel] udev virtio by-path naming
On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote: > >>>> One could argue about back-level compatibility, but virtio by-path > >>>> naming has changed multiple times. We have seen virtio-pci-virtio<n> > >>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It > >>>> might be a good time now
2020 Jun 13
2
Dovecot Replication Errors (only) when using tcps: as the mail_replica Protocol
Hi, I've been seeing errors logged for some time with replication processes, whereby replication sessions seem to be timing out periodically. This is with dovecot version 2.3.10.1 (a3d0e1171) and both are Gentoo x86_64. After some investigation I've determined that these timeouts are only ever occurring with tcps as the replication connection type. These errors never occur if
2017 Mar 01
2
[systemd-devel] udev virtio by-path naming
On Tue, Feb 28, 2017 at 08:39:07PM +0100, Lennart Poettering wrote: > On Tue, 28.02.17 19:28, Daniel P. Berrange (berrange at redhat.com) wrote: > > The problem with splitting these rules out into a separate project > > is that there's no other existing place that they would live. The > > "virtio people" as a group merely write specifications. The actual >
2017 Mar 01
2
[systemd-devel] udev virtio by-path naming
On Tue, Feb 28, 2017 at 08:39:07PM +0100, Lennart Poettering wrote: > On Tue, 28.02.17 19:28, Daniel P. Berrange (berrange at redhat.com) wrote: > > The problem with splitting these rules out into a separate project > > is that there's no other existing place that they would live. The > > "virtio people" as a group merely write specifications. The actual >
2013 Nov 14
2
is mounting subvolumes with a read-only root subvolume allowed?
Hi, I have a box with / and /home being subvolumes from the same btrfs filesystem. /etc/fstab: UUID=c0686... / btrfs subvol=root,x-systemd.device-timeout=0 1 1 UUID=c0686... /home btrfs subvol=home,x-systemd.device-timeout=0 1 1 ... / is initially mounted readonly by the initramfs, and then after switching to the real system, /home is attempted to be mounted in parallel with /
2012 Sep 16
1
doveadm backup - Fatal: All your namespaces have a location setting.
Hello list, I am using dovecot v2.1.9 and have a problem with doveadm backup: # doveadm backup -u user at domain.com maildir:/backup/domain.com/user/Maildir doveadm(user at domain.com): Fatal: All your namespaces have a location setting. It should be empty (default mail_location) in the namespace to be converted. Here my namespace config: namespace { list = children location =
2017 Feb 20
0
doveadm: Fatal: All your namespaces have a location setting
On 18.02.2017 18:49, Ben wrote: > Hi, > > I am trying to migrate mail from an old server and am receiving the > following error : > > doveadm(user at example.com): Fatal: All your namespaces have a location > setting. Only namespaces with empty location settings are converted. > (One namespace should default to mail_location setting) > > I found an old thread >
2017 Feb 20
1
doveadm: Fatal: All your namespaces have a location setting
> Hi! > > Can you post doveconf -n > > Aki # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.6.1.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1 first_valid_uid = 1000 mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject
2017 Feb 18
2
doveadm: Fatal: All your namespaces have a location setting
Hi, I am trying to migrate mail from an old server and am receiving the following error : doveadm(user at example.com): Fatal: All your namespaces have a location setting. Only namespaces with empty location settings are converted. (One namespace should default to mail_location setting) I found an old thread (http://www.dovecot.org/list/dovecot/2012-September/068269.html) that referred to
2008 Oct 16
5
virutal resources and ssh_authorized_key
Hello! I''ve got question - how to use ssh_autorized_key as a virtual resource? I''ve got bunch of users and ssh_authorized_key virtual resources, but only users gets to the target system - ssh keys not... I write something like: class admins { @user { "username": ... } @ssh_authorized_key { "username": ensure => present, key => "...",