It's easier to do with a src-nat within network gear. But let me tell you that this is referred to as "snowshoeing" as it expands your IP footprint, and is seen in the deliverability world as a slimy thing to do.
People do it to mitigate the effects of their IP addresses being blacklisted. But the cleaner solution is to ensure that the mail egressing from your platform shouldn't warrent a ban. On Thu, Feb 19, 2009 at 9:45 AM, Artem Bokhan <art...@academ.org> wrote: > Hi, can someone give me a hint how to randomly spread outgoing smtp traffic > over pool of ip-addresses? > As I understand it's necessary to create several transports and use > transport tables, but I do not see a way how to make lookups truly random. > > smtp1 unix - - n - 100 smtp -o > smtp_helo_name=smtpout1.do -o smtp_bind_address=1.1.1.1 > smtp2 unix - - n - 100 smtp -o > smtp_helo_name=smtpout2.do -o smtp_bind_address=2.2.2.2 > smtp2 unix - - n - 100 smtp -o > smtp_helo_name=smtpout3.do -o smtp_bind_address=3.3.3.3 > >