search for: protecthome

...at brain-force.ch> wrote: > > > Hello list > > I saw the response from Vlad in my queue (as dovecot was broken there > has been no delivery to mailbox) but after fix and queue flush Vlads > message does not show up in my mailbox. > > > Check the systemd unit for ProtectHome, and make sure that is turned > > off. > > Found these lines in unit file > > > # Enable this if your systemd is new enough to support it: > > ProtectSystem=full I recommend you leave this ON and instead set ProtectHome=false To enable writable /home Aki

On Fri, Dec 16, 2016 at 10:17:21AM -0800, Glenn E. Bailey III wrote: > This is a base install. If you deploy an instance in ec2 or GCE (ec2 > you can do the free tier) it's easily repeatable. Even on a RHEL 7.3 > instance. Note you'll need to allow root and password logins via SSH > before attempting. I can confirm this. The culprit? NetworkManager has /home open. I

Hi list I have to dovecot instances running which host my mailboxes on Centos7 dovecot.x86_64 1:2.2.26.0-2.el7.centos installed dovecot-debuginfo.x86_64 1:2.2.26.0-2.el7.centos installed dovecot-mysql.x86_64 1:2.2.26.0-2.el7.centos installed dovecot-pigeonhole.x86_64 1:2.2.26.0-2.el7.centos installed all over sudden both dovecot

On Fri, Dec 16, 2016 at 02:29:28PM -0500, Jonathan Billings wrote: > The culprit? NetworkManager has /home open. I can't figure out > *WHY*. NetworkManager.service has 'ProtectHome=read-only', which keeps NM from writing there. I presume namespacing /home in this way counts against unmounting it. This is a good security protection for everyone running NM, so I can see it being worth the tradeoff vs. being able to move or remove /home on a live system. (It also has Protec...

...7.3). On Tue, Dec 20, 2016 at 11:07 AM, Matthew Miller <mattdm at mattdm.org> wrote: > On Fri, Dec 16, 2016 at 02:29:28PM -0500, Jonathan Billings wrote: >> The culprit? NetworkManager has /home open. I can't figure out >> *WHY*. > > NetworkManager.service has 'ProtectHome=read-only', which keeps NM from > writing there. I presume namespacing /home in this way counts against > unmounting it. This is a good security protection for everyone running > NM, so I can see it being worth the tradeoff vs. being able to move or > remove /home on a live system....

On Tue, Dec 20, 2016 at 02:07:03PM -0500, Matthew Miller wrote: > If you wanted to change this, drop ProtectHome=false into > /etc/systemd/system/NetworkMananger.service.d/override.conf (possibly > by using sudo systemctl edit foo NetworkMananger). Sorry, no "foo" ? that was a cut-paste error. And as Jonathan says, make sure to spell NetworkManager right. :) sudo systemctl edit NetworkMana...

...4.833067] usb 3-2: Manufacturer: Cypress Semiconductor [10684.875129] generic-usb 0003:0665:5161.0005: hiddev96,hidraw3: USB HID v1.00 Device [Cypress Semiconductor USB to Serial] on usb-0000:00:1a.2-2/input0 maybe there exists such an implementation for usb already. last time i implemented the protecthome driver i found bestups to be what i actually wanted but then i already invested a lot of time in writing protecthome.c; === summary === maybe someone can help me with this problems. i will post a spec of what i have found so far in my blog soon. thanks in advance

Greetings! I'm having a bit of trouble trying out Dovecot 2.3 on CentOS 7. Dovecot 2.2.33 works fine on the same system (same config as well, minus the SSL changes) but after upgrading to 2.3 I'm getting the following errors: Feb? 1 21:30:18 localhost dovecot: imap(reio at bwo.mrstuudio.ee)<3566><FoOsnStkXt4KAAgC>: Debug: INBOX.Templates: Mailbox opened because: STATUS

Hello list I saw the response from Vlad in my queue (as dovecot was broken there has been no delivery to mailbox) but after fix and queue flush Vlads message does not show up in my mailbox. > Check the systemd unit for ProtectHome, and make sure that is turned > off. Found these lines in unit file > # Enable this if your systemd is new enough to support it: > ProtectSystem=full and after commenting the 2nd one, dovceot could write again to the FS :-) Have no idea why this setting started to make problems just tod...

/etc/systemd/system/dovecot.service.d/writable-home.conf [Service]ProtectHome=false maybe this helps? ---Aki TuomiDovecot oy -------- Original message --------From: Reio Remma <reio at mrstuudio.ee> Date: 01/02/2018 21:44 (GMT+02:00) To: dovecot at dovecot.org Subject: Dovecot 2.3 on CentOS 7. Greetings! I'm having a bit of trouble trying out Dovecot 2.3 on Ce...

...d was: [Service] ReadWriteDirectories=/home/dovecot What would be the preferred directory for storing all virtual mail without modification to system files? Thanks! Reio On 01.02.2018 21:57, Aki Tuomi wrote: > /etc/systemd/system/dovecot.service.d/writable-home.conf > > [Service] > ProtectHome=false > > > maybe this helps? > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Reio Remma <reio at mrstuudio.ee> > Date: 01/02/2018 21:44 (GMT+02:00) > To: dovecot at dovecot.org > Subject: Dovecot 2.3 on CentOS 7. > &gt...

Am 19.03.2020 um 16:28 schrieb Adam Raszkiewicz: > I was able to solve errors below but now it complains about the startup how is handled on Centos7: > > ? dovecot.service - LSB: Dovecot init script > Loaded: loaded (/etc/rc.d/init.d/dovecot; bad; vendor preset: disabled) > Active: failed (Result: exit-code) since Thu 2020-03-19 15:15:37 UTC; 54s ago > Docs: