currently we get “egress_source”:“ip-1” . this ip name i need ip address in log . any option to get this ?
change the ip-1 to ip add in string hope this will help you
Yes, names are arbitrary, it is a good practice to use meaningful names, and that can include IP information.
Ok . thanks @youthful-zorse @yearning-hyena
Hi @yearning-hyena @youthful-zorse We are using multiple IPs in a pool. Is there any option to specify an IP while sending an email?
The whole idea of a pool is its members can be used together.
What is the use case for targeting one member?
I want senting ip & pool details on “Reception” event. currently senting ip & pool details only get “Delivery” or “Bounce” event. This is my usecase . (Expecting senting ip in all events)
Only deliveries use a sending IP, sending IP isn’t relevant to receiving a message.
Any IP address available will be in the “peer_address” object. This will only be reported if it is available.
// the submitter or the receiver, depending on the record type
"peer_address": {
// When delivering, this is the name from the MX record.
// When receiving, this is the EHLO/HELO string sent by
// the sender
"name": "gmail-smtp-in.l.google.com.",
"addr": "142.251.2.27"
},
@kindhearted-deer is this question resolved?
Yes