Wietse Venema <wietse <at> porcupine.org> writes: > It is not a major effort to give those cache entries a finite > time-to-live but this needs a better justification that what appears > to be an attempt to circumvent Yahoo rate limits.
I have a need similar to the original poster. In my case the use case is to gradually move outgoing traffic to a new egress IP. I have separate transports set up in master.cf per address like this: smtp unix - - - - - smtp out1 unix - - - - 50 smtp \ -o smtp_bind_address=10.150.15.101 out2 unix - - - - 50 smtp \ -o smtp_bind_address=10.150.15.102 [...] and additionally the senders are partitioned across IPs with sender_dependent_default_transport_maps Moving a big chunk of traffic in one go to a new IP that was never sending any traffic before will just cause it to get greylisted or blocked altogether. Given I have a low number of high-volume senders, I cannot find an easy way to start sending (say) 1% of given sender's traffic from a new IP. Any suggestions? Marcin
