> I have never used a Foundry Load Balancer so my response may > be way off. I am assuming it is not functioning as a MTA, but > is simply rewriting the source IP portion of packets.
Correct but it only does this at the IP level, not at the SMTP protocol level. In other words, Windows IP gets the TCP connection from the load balancer's IP but the SMTP protocol (Payload of the TCP communication) shows the sending SMTP server in any of the communication. So it sounds like I need to configure DSR. Thx > If the source IP of incoming packets destined to your declude > gateways is replaced with that of your load balancer, it does > not constitute an additional hop as far as declude is > concerned. The message header will likely report the > connecting IP address (in this case, being that of your load > balancer if doing source NAT) but also with the sending MTA's HELO. > > The IP tests including RBL lookups and SPF checks are based > on the last reported sending MTA's IP address. Also, other > DNS tests such as REVDNS won't mean much of anything anymore > since declude will only be checking for a PTR for the IP of > your load balancer. Non-IP based tests should work fine I would think. > > As much of a pain as it might be, I would stick with DSR if > you don't want to lose declude's IP-based tests. > > Landon > > > > --- > This E-mail came from the Declude.JunkMail mailing list. To > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and > type "unsubscribe Declude.JunkMail". The archives can be > found at http://www.mail-archive.com. > --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
