[quote user="GLM"]Hello, <blockquote><div>The MX servers of one of our main clients are experiencing a weird problem: our TCP connection at their port 25 is correctly established, but their 220 reply comes after a big delay (about 4 minutes). Of course, our MercuryE timeouts. I know there is a setting to control MercuryE's TCP/IP timeout. I am wondering if there is a setting to force MercuryE to wait ("indefinitely") for their first 220 reply. </div></blockquote><div>You can't have it wait forever nor would you really want to anyway.  Set the MercuryE TCP/IP timeout to something like 300 seconds to give the server time to respond.  If the 5 minutes is to low then double it to 600 seconds. </div><blockquote><div>Thanks in advance. </div><div>Gonzalo López Menéndez</div><div><a href="mailto:gonzalo.lopez@gmeana.com" mce_href="mailto:gonzalo.lopez@gmeana.com">gonzalo.lopez@gmeana.com</a></div><div>GADD-GRUPO MEANA, S.A.[/quote]</div></blockquote>

<DIV>Hello,</DIV> <DIV> </DIV> <DIV>The MX servers of one of our main clients are experiencing a weird problem: our TCP connection at their port 25 is correctly established, but their 220 reply comes after a big delay (about 4 minutes). Of course, our MercuryE timeouts. I know there is a setting to control MercuryE's TCP/IP timeout. I am wondering if there is a setting to force MercuryE to wait ("indefinitely") for their first 220 reply. </DIV> <DIV> </DIV> <DIV>Thanks in advance.</DIV> <DIV> </DIV> <DIV>Gonzalo López Menéndez</DIV> <DIV><A href="mailto:gonzalo.lopez@gmeana.com">gonzalo.lopez@gmeana.com</A></DIV> <DIV>GADD-GRUPO MEANA, S.A.</DIV> <DIV> </DIV>