User hestiaweb generating *** SECURITY information for HOSTNAME *** messages

Community Support
1

hestiaweb@HOSTNAME and root@HOSTNAME keep generating multiple unrouteable emails (several per second).

These messages are all being immediately frozen and looking at the mail logs, appear to have the Subject “*** SECURITY information for HOSTNAME ***”

I read something about File Manager security messages but I’m not using the file manager so I have no idea what’s generating these. I have no mail accounts on the server either. The server has only been online for 72 hours.

The messages are being received “from Debian-exim by HOSTNAME with local (Exim 4.96)” and “from hestiaweb by HOSTNAME with local (Exim 4.96)”

Hestia v1.8.3 on Debian 12.9 (x86_64)

2

Is there a way to see which scripts are generating mails? It appears that these messages are being generated automatically by Hestia, sometimes at a rate of 10 per second.

3

You can view the headers and body of those emails. That might give you a clue about what’s going on.

To list messages in queue:

exim4 -bp

To view headers and body:

exim4 -Mvh HereTheMessageID
exim4 -Mvb HereTheMessageID
4

Thanks. Not very interesting I’m afraid. Doesn’t give me any clues as to what’s generating these messages. Just an endless loop of messages being generated and return to sender…

Received: from Debian-exim by HOSTNAME with local (Exim 4.96)
id 1tuP3Z-000j12-19
for hestiaweb@HOSTNAME;
Tue, 18 Mar 2025 05:00:01 +0000
X-Failed-Recipients: root@HOSTNAME
Auto-Submitted: auto-replied
From: Mail Delivery System Mailer-Daemon@HOSTNAME
To: hestiaweb@HOSTNAME
References: E1tuP3Z-000j0F-0f@HOSTNAME
Content-Type: multipart/report; report-type=delivery-status; boundary=1742274001-eximdsn-1772776744
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: E1tuP3Z-000j12-19@HOSTNAME
Date: Tue, 18 Mar 2025 05:00:01 +0000

5

Check the body and also this message E1tuP3Z-000j0F-0f

6

Thank you! I feel like I’m getting somewhere now. So simple but after working all day, I think my brain stopped functioning!

hestiaweb : unable to resolve host HOSTNAME: Name or service not known

Now I just need to look at all the places where the hostname is set and find out why it only saved the local part.

1 Like
7

And now fixed simply by using v-change-sys-hostname. So simple!

Thank you

2 Likes
8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.