When I am sending any mails reception logs, don’t contains any egress_pool as I am assinging the pool to that perticular tenant.
Hey there @youthful-zorse, thanks for posting. Please read the “Troubleshooting” and “How to Ask for Help” buttons below. If you would like a 1:1 support session from the KumoMTA team, details are at the “Book a Support Session” button below.
If requied I can share the logs as well.
{“type":“Reception”,“id”:“7cbdee9ce2b511eebde10aa6b44afef4”,“sender”:"test@comm.acl.pinchappmails.com”,“recipient”:"zeref@gmail.com",“queue”:"ses@gmail.com",“site”:“”,“size”:1443,“response”:{“code”:250,“enhanced_code”:null,“content”:“”,“command”:null},“peer_address”:{“name”:“ip-10-4-1-71.ap-south-1.compute.internal”,“addr”:“127.0.0.1”},“timestamp”:1710497960,“created”:1710497960,“num_attempts”:0,“bounce_classification”:“Uncategorized”,“egress_pool”:null,“egress_source”:null,“feedback_report”:null,“meta”:{“tenant”:“ses”},“headers”:{“Subject”:“test Fri, 15 Mar 2024 15:49:20 +0530”},“delivery_protocol”:null,“reception_protocol”:“ESMTP”,“nodeid”:“aa2e6bbb-a3c4-41b3-8d4d-2c7d8c044622”}
I am using stable build.
egress means “going out”. Egress related metadata is not assessed for a message until it is attempted for delivery. It is not applicable during reception because reception is “ingress” (coming in). In KumoMTA, you don’t assign a message to an egress pool, you assign it to a queue that is in turn associated with an egress pool via events that run after reception and that can use arbitrary lua logic to decide how to configure the egress path. We don’t and can’t know the egress pool at the time of reception.
ok got it thanks