Files
kumomta/docs/reference/events/xfer_message_received.md
T
Wez Furlong 07ab3d44a3 inject+xfer: cut over to AuthInfo from AuthKind
Replace the older type with the newer one.

Serialize a copy of auth_info when handling deferred generation,
so that we have a lossless representation of that state when
we eventually process the request.  That doesn't change really
anything today, but will enable more granular ACL checks in
the future.

Pass the auth_info through to the http_message_generated and
xfer_message_received events to enable more granular access
control policies to be scripted.
2025-12-18 10:19:09 +00:00

884 B

xfer_message_received

{{since('2025.12.02-67ee9e96')}}

kumo.on('xfer_message_received', function(message, auth_info) end)

Called during reception of a message transfer (xfer) from another kumomta, just prior to inserting the message into the appropriate queue.

This event provides the opportunity to assess and otherwise update the message metadata to make it suitable for processing on the current node.

For example, you may choose to alter queue related metadata items to match the current state of the world on the receiving server.

Any errors that are raised by the event handler will cause the message xfer to transiently fail; the sending side will retry it according to its retry schedule.

The auth_info parameter is an AuthInfo object that can be used to implement more granular access policies. {{since('dev', inline=True)}}