:-)

On 11/14/18 11:25 PM, Viktor Dukhovni wrote:
On Nov 14, 2018, at 5:14 PM, Marek Kozlowski <m.kozlow...@mini.pw.edu.pl> wrote:

Your kernel's UNIX-domain stack is messed up, or some 'security'
system is interfering with proper operation.

https://dilbert.com/strip/1995-06-24

Well. I've disconnected spamskurwysyn (I mean: spamassassin) - in master.cf:
smtp      inet  n       -       n       -       -       smtpd
#  -o content_filter=spamassassin
   -o receive_override_options=no_address_mappings

I mean:
smtp      inet  n       -       n       -       -       smtpd
#  -o content_filter=spamassassin
#  -o receive_override_options=no_address_mappings

This makes no difference, the Dilbert verdict remains unchanged.

Well, yes and no.
I've investigated the problem a little bit and it seems that the heart of the problem is no unix_trigger sent from sendmail to qmgr due to a broken pipe. As a result qmgr waits for a timer. OK, seems like something wrong with the system. Unfortunately hardware/system upgrade won't solve the problem. Why? The hardware is more than strong enough. The system is up-to-date.

I've been running postfix for a long time in a systemd Linux under virtual machine (qemu+kvm). I'm starting to suppose it is not a hardware itself; it's something related to systemd or qemu. I'm wondering if there are some users running postfix with no problems under the most recent systemd (which in fact IS a kind of magic)? using postfix on a guest over qemu? using postfix on a virtualized systemd system?

Best regards,
Marek

--
Dr Eng. Marek Kozłowski
Senior Lecturer
Unix and Network Administrator
Warsaw University of Technology
Faculty of Mathematics and Information Sciences
ul. Koszykowa 75,
00-662 Warszawa
POLAND
tel.: +48 601 827 225

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to