# One more error; sieve-spam.svbin

**URL:** <https://discourse.mailinabox.email/t/one-more-error-sieve-spam-svbin/11869>\
**Category:** uncategorized\
**Created:** [May 6, 2024, 8:52pm UTC](https://discourse.mailinabox.email/t/one-more-error-sieve-spam-svbin/11869 "2024-05-06T20:52:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Keith\_Rettig](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/k/3bc359/32.png) [@Keith\_Rettig](https://discourse.mailinabox.email/u/Keith_Rettig)\
**Post date:** [May 6, 2024, 8:52pm UTC](https://discourse.mailinabox.email/t/one-more-error-sieve-spam-svbin/11869/1 "2024-05-06T20:52:09Z")

</div>

See lines like this constantly in my mail log.

May 06 13:48:24 lmtp([email@domain.net](mailto:email@domain.net))\<158538\>: Error: open(/etc/dovecot/sieve-spam.svbin.mail.ppgcloud.com.158538.95b83c4993ba03e1) failed: Read-only file system

May 06 13:48:24 lmtp([email@domain.net](mailto:email@domain.net))\<158538\>: Error: sieve: binary /etc/dovecot/sieve-spam.svbin: save: failed to create temporary file: open(/etc/dovecot/sieve-spam.svbin.) failed: Read-only file system

May 06 13:48:24 lmtp([email@domain.net](mailto:email@domain.net))\<158538\>: Info: sieve: msgid=[f42094d0d2610fa27ec2610a001ff329@customersclientdomain.com](mailto:f42094d0d2610fa27ec2610a001ff329@customersclientdomain.com): stored mail into mailbox ‘INBOX’

Is there a permissions issue I should fix?

Keith.

---

<div class="post-metadata">

**Author:** ![BenCranston](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/b/958977/32.png) [@BenCranston](https://discourse.mailinabox.email/u/BenCranston)\
**Post date:** [August 1, 2024, 12:37am UTC](https://discourse.mailinabox.email/t/one-more-error-sieve-spam-svbin/11869/2 "2024-08-01T00:37:13Z")

</div>

Same things started for me after the upgrade to v69b. Not sure what to make of it, but each new email passing thru the system triggers this series of errors for me.

```auto
Jul 31 20:15:12 lmtp(user@domain.net)<21283><6LOhA4/TqmYjUwAA/eBZpA>: Error: open(/etc/dovecot/sieve-spam.svbin.box.domain.net.21283.36b8347f1456ac6f) failed: Read-only file system
Jul 31 20:15:12 lmtp(user@domain.net)<21283><6LOhA4/TqmYjUwAA/eBZpA>: Error: sieve: binary /etc/dovecot/sieve-spam.svbin: save: failed to create temporary file: open(/etc/dovecot/sieve-spam.svbin.) failed: Read-only file system

```

---

<div class="post-metadata">

**Author:** ![BenCranston](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/b/958977/32.png) [@BenCranston](https://discourse.mailinabox.email/u/BenCranston)\
**Post date:** [August 1, 2024, 2:26pm UTC](https://discourse.mailinabox.email/t/one-more-error-sieve-spam-svbin/11869/3 "2024-08-01T14:26:43Z")

</div>

I think I might be on to something… It would appear that the systemd service for dovecot is set to

```auto
ProtectSystem=full

```

which in turn according to the docs I’m reading [systemd](https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#ProtectSystem=) says that setting will result in the /etc hierarchy being mounted as read only for the service. To me that’s the core issue. I’m not sure the correct path forward perhaps @JoshData can provide guidance.

---

<div class="post-metadata">

**Author:** ![BenCranston](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/b/958977/32.png) [@BenCranston](https://discourse.mailinabox.email/u/BenCranston)\
**Post date:** [August 12, 2024, 8:45pm UTC](https://discourse.mailinabox.email/t/one-more-error-sieve-spam-svbin/11869/4 "2024-08-12T20:45:36Z")

</div>

I added the above findings to an open issue over on github.`[lmtp error - read-only filesystem](https://github.com/mail-in-a-box/mailinabox/issues/1571)`