Relaying limits (count?) not working in 2.18pro

Issue #489 closed
Alexander created an issue

Since upgrading to 2.18pro from 2.14pro, counting relaying limits per per relayed IP/network stopped working - the counter remains at 0.

As I'm using bridge mode in docker, all traffic goes via 127.0.0.1 and 172.17.0.1 (as listed in the delivery logs). So I have setup up a limit for each of these IPs - and that worked perfectly in 2.14pro - it does not anymore in 2.18pro.

Comments (7)

  1. SH repo owner

    "all traffic goes via 127.0.0.1 and 172.17.0.1"

    Poste needs to know what is source IP of connections and docker is hiding it - this is problem of docker configuration not poste.

  2. Alexander reporter

    Why would this work in 2.14pro then? According to the delivery logs, my installation sees all traffic either coming from 127.0.0.1 or 172.17.0.1.

  3. SH repo owner
    • the unknown source addressess are bigger problem - it seems that your docker installation use userland-proxy - you should disable userland proxy and switch to nating, or better use network mode "host" (there are lot of plugins depending on source ip address that I am suprised it is running without major issues)
    • 127.0.0.1 is unmetered by default (it would apply to internal mailserver messages, it doesn't make sense)
    • only realyed IPs are counted, so if 172.17.0.1 is not relayed then it will not be counted (don't add it to relayed IPs! It would create open relay)
  4. SH repo owner

    There were some changes at 2.15, I think I know where is problem with counting. Can you please delete limit and create it again? (though only 172.17.0.1 should be working if it is relayed)

  5. Log in to comment