Community Discussions and Support
MercuryE (end-to-end) in a multihomed server.

You should be able to convince Windows to prefer a certain gateway or interface by setting a lower metric for it:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/route.mspx?mfr=true 

/Rolf 

<p>You should be able to convince Windows to prefer a certain gateway or interface by setting a lower metric for it:</p><p><a href="http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/route.mspx?mfr=true">http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/route.mspx?mfr=true</a> </p><p>/Rolf </p>

I added a new IP address to my server to host an additional service, and i natted it to additional public IP address.

Then i noticed that some mails were sent using original IP, some other using new IP !

It is possible to link MercuryS, MercuryP, MercuryI modules to a specific IP using "IP interface to use:" option, but that option seem not to be present in the MercuryE module.

Is there an option or workaround to impose SMTP end-to-end client to use a specific IP address ?

Thanks - Alex.

<P>I added a new IP address to my server to host an additional service, and i natted it to additional public IP address. </P> <P>Then i noticed that some mails were sent using original IP, some other using new IP !</P> <P>It is possible to link MercuryS, MercuryP, MercuryI modules to a specific IP using <EM>"IP interface to use:"</EM> option, but that option seem not to be present in the MercuryE module.</P> <P>Is there an option or workaround to impose SMTP end-to-end client to use a specific IP address ?</P> <P>Thanks - Alex.</P>

MercuryE is a client, not a server, so it doesn't bind to any specific IP interface. Have a look at the routing rules in Windows, though, it should be possible to set priorities for interfaces there.

/Rolf 

<p>MercuryE is a client, not a server, so it doesn't bind to any specific IP interface. Have a look at the routing rules in Windows, though, it should be possible to set priorities for interfaces there.</p><p>/Rolf </p>

[quote user="Rolf Lindby"]

MercuryE is a client, not a server, so it doesn't bind to any specific IP interface. Have a look at the routing rules in Windows, though, it should be possible to set priorities for interfaces there.

/Rolf 

[/quote]

Thank you Rolf.

The problem is not so trivial, since some servers act the MX reverse to identify spammers ... so i believe important to communicate using the right IP ...

 Alex.

[quote user="Rolf Lindby"] <P>MercuryE is a client, not a server, so it doesn't bind to any specific IP interface. Have a look at the routing rules in Windows, though, it should be possible to set priorities for interfaces there.</P> <P>/Rolf </P> <P>[/quote]</P> <P>Thank you Rolf.</P> <P>The problem is not so trivial, since some servers act the MX reverse to identify spammers ... so i believe important to communicate using the right IP ...</P> <P> Alex.</P>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft