How can I remove the following header information from Kumomta?
Received: from [127.0.0.1] (127.0.0.1)
by wrn.xxxx.xx (KumoMTA 127.0.0.1)
with ESMTP id 46f997e771be11f0870ea618c9a60124 for ;
Tue, 5 Aug 2025 05:37:29 +0000
It has been changed to false, but two received mail headers still appear.
init.lua
…
kumo.start_esmtp_listener {
listen = ‘127.0.0.1:25’,
hostname = ‘domain.com’,
relay_hosts = { ‘127.0.0.1’ },
trace_headers = {
received_header = false,
supplemental_header = false,
header_name = ‘X-KumoRef’,
},
}
end)
Need to restart kumomta.
It turns out that the configuration file is not applied in real time. Thank you very much.
Most changes take 10 minutes to update. However, some start_esmtp_listener wait for init to need to be restarted.
Thank you very much, I did it! Have a nice day.
Next, I need to slowly learn how to configure SMTP AUTH.
Brother, I would like to ask you a question. This is someone else’s email header. Why does it contain the following additional content?
by srv125687.hosttoname.com (KumoMTA 127.0.0.1) with ESMTP id faec44526edc11f0b85200163c032c57 for <domain.com>; Fri, 1 Aug 2025 13:39:43 +0000
Authentication-results ezweb.ne.jp; dmarc=none header.from=domain.com; dkim=pass; spf=fail smtp.mailfrom=domain.com; sender-id=Fail (pra) header.From=domain.com
X-razorgate-vade gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgddutdefkeefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecumffffffkpdfgpfggqdetfgenuceurghilhhouhhtmecupfdsteenucgolfgrphgrnhdqqdflrfdqufhushhpvggtthfrrghtthgvrhhnqdffvdelucdlhedmnegolfgrphgrnhdqqdflrfdqufhushhpvggtthfrrghtthgvrhhnqdfjtdegucdlvddtmdenjfgrmhfjvggruggvrhfhihgvlhguucfjvggruggvrhcuufgtohhrihhnghculddquddtmdenucfjughrpeffvffhuffkofgtgfesthektddtredtjeenucfhrhhomhepsghinhgrnhgtvgcuoehtihgtkhgvthesshgrmhgvnhhshhhophdvgedruggvqeenucggtffrrghtthgvrhhnpeefgfdvffeftedtgfeujeduhefgteejledvgeegueeivdehvdejhfevheefjeegveenucfkphepudelfedrgeefrddutdegrddugeeinecuvehluhhsthgvrhfuihiivgepgeenucfrrghrrghmpehhvghlohepshhrvhduvdehieekjedrhhhoshhtthhonhgrmhgvrdgtohhmpdhinhgvthepudelfedrgeefrddutdegrddugeeipdhmrghilhhfrhhomhepthhitghkvghtsehsrghmvghnshhhohhpvdegrdguvgdprhgvvhfkrfepmhhtnhdtrdhmuhhllhhitggrnhhflhhoohhrihhnghhsrdgtohhmpdhsphhfpehfrghilhdpughkihhmpehprghsshdpghgvohfkrfepfffgpdfovfetjfhoshhtpegruhdqphhusgdqnhgrohdqfidurgdq rghuphhusgdqtdekfedpnhgspghrtghpthhtohepuddprhgtphhtthhopedtvghufedvleefuddthedtuddqlehvsegviiifvggsrdhnvgdrjhhp
X-razorgate-vade-verdict clean 15
X-razorgate-vade-classification clean
X-kumoref eyJfQF8iOiJcXF8vIiwicmVjaXBpZW50IjoiMGV1MzI5MzEwNTAxLTl2QGV6d2ViLm5lLmpwIn0=
That email passed through Vade (Hornet Security) filter and that is showing you the filter result. The long encoded string is meant to be read my Vade. The important part is that the verdict is “clean”
Is this header content added by the recipient? Or is it added by the sender?
It could be either. Typically the receiving MTA, but not always.
It’s possible, but the recipient’s email address is mine. I tested sending an email from Kumomta to my own email address, but the header content was missing. I think it must have gone through an anti-spam system during transmission. Can Kumomta integrate this anti-spam system?
If you sent it directly from one server to another then this header should not have been formed. It is possible to integrate Vade but I doubt you did that since I have not documented it yet.
It is very likely you sent this though other servers that were running the Vade AV/AS filter which added these headers. Our native deployment does not use the x-razorgate headers.