The deliverability tab lists the local docker IPs as missing from SPF, but those IPs do not send mail. It should only check for either an mx mechanism or the public IP(s) of the MTA.
Versions
server 27.1-rc.23
console 27.1-rc.17
The deliverability tab lists the local docker IPs as missing from SPF, but those IPs do not send mail. It should only check for either an `mx` mechanism or the public IP(s) of the MTA.
Versions
server 27.1-rc.23
console 27.1-rc.17
<img width="774" alt="Screenshot 2026-11-16 at 6.23.07 PM.png" src="attachments/5063d4b4-4991-493c-804f-f686a04ae106">
Thanks, you're right: those are the server container's own addresses, not ones it sends from. With no source addresses set, the check uses what the server's name resolves to, and inside the container that name points at the container itself. The fix is in the server: inbuxa/inbuxa-server#408. The SPF failures for 172.31.253.10 and fd69:6e62:7578::2 can be ignored until then.
Thanks, you're right: those are the server container's own addresses, not ones it sends from. With no source addresses set, the check uses what the server's name resolves to, and inside the container that name points at the container itself. The fix is in the server: inbuxa/inbuxa-server#408. The SPF failures for 172.31.253.10 and fd69:6e62:7578::2 can be ignored until then.
Fixed in the server, inbuxa/inbuxa-server#409, released in server 27.1-rc.25. Deliverability no longer tests the container's own addresses; it uses what DNS says your server's name is. The next daily check (or Check now) after upgrading clears those two SPF failures. Thanks for the report.
Fixed in the server, inbuxa/inbuxa-server#409, released in server 27.1-rc.25. Deliverability no longer tests the container's own addresses; it uses what DNS says your server's name is. The next daily check (or Check now) after upgrading clears those two SPF failures. Thanks for the report.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The deliverability tab lists the local docker IPs as missing from SPF, but those IPs do not send mail. It should only check for either an
mxmechanism or the public IP(s) of the MTA.Versions
server 27.1-rc.23
console 27.1-rc.17
Thanks, you're right: those are the server container's own addresses, not ones it sends from. With no source addresses set, the check uses what the server's name resolves to, and inside the container that name points at the container itself. The fix is in the server: inbuxa/inbuxa-server#408. The SPF failures for 172.31.253.10 and fd69:6e62:7578::2 can be ignored until then.
Fixed in the server, inbuxa/inbuxa-server#409, released in server 27.1-rc.25. Deliverability no longer tests the container's own addresses; it uses what DNS says your server's name is. The next daily check (or Check now) after upgrading clears those two SPF failures. Thanks for the report.