There's a couple different and easy ways to do this :

Just add the new IP to the server.  Add a g_gateway entry for all email 
and bind that to the new IP.  Then all you need is to add to your DNS an 
A and PTR record for the new IP.   MX and everything else stays the 
same.  All you're trying to do is get surge to use a different IP to 
send with.

Optionally you can set g_bind_out  to get surge to "send" on the new IP. 
  You still need the new DNS entries.  This is the way we do it with 
multi-homed servers behind load balancing.  g_bind_out can take a comma 
separated list and both ip4 and ip6.

Food for thought ?

--Ed

On 09/20/2013 02:59 PM, David Camm wrote:
> thanks for the suggestions, but neither gatewaying to another server nor
> changing the ip is viable for me.
>
> a) i don't have another server to gateway TO and
>
> b) the server is multi-homed already. just adding another ip will not
> get surge to use it. i'd have to reconfigure networking, change the dns
> that points to the server AND get my colo facility to change their
> reverse dns entry.
>
> david camm
> advanced web systems
> keller, tx
>
>
>
>
>

-- 
-----------------------------------------------------------
EAS Enterprises LLC
World Class Web and Email Hosting Solutions
IPv6 ready today for your needs of tomorrow!
Ask us about dual-stacking your site
www.easent.net