> Am 20.08.2018 um 18:10 schrieb Wietse Venema <wie...@porcupine.org>: > > Christian Ro??ner: >> What key is the log message talking about? > > Postfix asks the kernel to create a queue file, and the kernel > returns the ENOKEY error code. Postfix is not responsible for > eCryptfs key management.
It is ext4 encrypted directory with e4crypt. Anyways: If I have copied over all files and directories from .../old/postfix* as explained step by step, then why does that work and if Postfix wants to create a file, it fails? It is not chroot. > Maybe there is a problem with the startup order, where Postfix > starts before eCryptfs? Easy enough to check by stopping and staring > Postfix by hand after the system is up. My plan is to not put Postfix (and Dovecot) into the runlevels. So system boots and I enter the passphrase. After that I want to start the services. Could it be some ext4 feature that Postfix misses? I had to add encrypt with tune2fs to the partition: tune2fs -O encrypt /dev/vg01/lv_var I have tested the encryption stuff with a test-folder under /var/spool/test. The same way, as described for the Postfix-spool directories. I can create files under this test folder and edit them. So in principal all is working. Only Postfix seems to have trouble. So the reason for asking here on the list. I also could not find anything related with Google. Is there nobody, who could reproduce this? Christian -- Rößner-Network-Solutions Karl-Bröger-Str. 10, 36304 Alsfeld T: +49 6631 9110725, F: +49 6631 78823409, M: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner-network-solutions.com
smime.p7s
Description: S/MIME cryptographic signature
