postalserver
Mail forwarded by routers does not use IP pools
Describe the bug
Forwarded emails received by routes do not use IP pools to send messages.
To Reproduce
- Enable and configure IP pools
- Add a route with an address endpoint
- Send an email to the address, the forwarded email is sending by system's default IP address
Screenshots
I'm going to file this as a bug, mostly because I don't know enough about IP Pools, hopefully someone will be able to investigate and confirm where things are getting confused.
hello I have the same problem, I configure the IP pool in postal, this is displayed at the top of the panel and I add my IPs, however, when I check the sender of my email it always mentions the main IP of the server (x.x.x.x.1) so it does not seem to be working the pool. This is very strange since in the sent mail panel, the message shows in parenthesis (from x.x.x.x.2) but the sender when I check it either in gmail, outlook, etc. it always shows the main IP of the server (x.x.x.x.1). Is this a bug or could it be a configuration problem on my part?
I enabled the IP pool in the postal.yml with use_ip_pools: true
I configure the main IP and the secondary IP in the same IP pool (the main is with priority 1 and the secondary 100 so they should only come out of the secondary IP), then I add it to my organization and then to my mail server which shows that it has assigned this IPS pool, however it doesn't seem to be working properly.
