I Folks,

I have been trying this with different versions of the SpamFilter, but never got it to fly.

I use one Ethernetcard and assign it multiple IP addresses. I want Exchange to use on and SpamFilter the other. I made very sure that the Exchange SMTP Server runs on a specific IP, assigned SpamFilter the other IP address. Still, SpamFilter *thinks* that SMTP is running on the same IP as it and can not bind the port.

As anyone figured out how this works and can post detailed instructions?

Thanks

Martin

Well,

the main reason for two IP's using port 25 is that if one server fails, at least the other one still accepts the eMails, this is subsequently also an issue for MX records in DNS.

I wonder why I have explicitly changed Exchange to use one specific address and SpanFilter to use another and that just simply doesn't work.

I doubt this to be a protocol issue. Having done quite some sockets programming, the binding of the address and port is simply failing.

Maybe I give it a shot with your config over the Holidays and see how it works for me.

Thanks

Sean,

I was refering to the SpamFilter or Exchange Server failing, not the physical machine. There I agree it would be useless. I currently have SpamFilter running on a seperate machine and it is the main MX eMail receiver and Exchange the fallback MX. Still, I would much like to consolidate both onto one machine with fallback option and since I can't have a pysical port associated to an MX record (to the best of my knowledge) this isn't an option if I need to use different ports.

Your are correct on the MX port config thing, did you read through the tech document yet that Roberto has put together?

http://www.logsat.com/sfi-technical-details.asp" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - http://www.logsat.com/sfi-technical-details.asp" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - http://www.logsat.com/sfi-technical-details.asp

Also, Why not drop in an addition Ethernet card? insted of fooling with mult IPs on a single card. This would help incase one card fails too.

Thanks Sean,

I will read through it. Reason for two (actually more IP's) on one Ethernet is that I use this Card for WAN access as I have NAT enabled on the other for LAN, still I do remember having this given a shot some time ago, but the result was the same. Though I wouldn't bet any money on the correct configuration back when. Maybe I assign another public IP to my LAN, do a bit of rewiring and give that a shot, just to be sure, but I doubt that will make much of a difference.

And as to the Document, this describes more the DSN and that isn't where the problem truly is.

Martin

No Problem Sean,

thanks for the hints. If I get that to fly properly, I let you know. Just hate to use different ports, but if the two physical cards do the trick, then that will work for me, assuming NAT isn't screaming at me. Since I run a Wireless LAN as well I wouldn't want to spend all weekend to get this fancyed out. I have W2K Server, Exchange 2000, IIS and a few other things running on that Server and changing all this wouldn't be what I consider weekend fun.

Don't call me un-romantic, I have been in IT for about 15 years and had enough weekends working :)

Not sure if this will help, but we had the same issue. See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;281760&Product=exch2k" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - http://support.microsoft.com/default.aspx?scid=kb;en-us;281760&Product=exch2k" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - http://support.microsoft.com/default.aspx?scid=kb;en-us;281760&Product=exch2k

- Al

Hi Al,

that seems to be right on the mark. I defnitly check it out!!!!!

Thanks a lot, maybe something LogSat should include in their Documentation or link to.

Martin

Thanks again Al,

that did the trick.

Martin