On Thursday 16 December 2004 09:16 am, Lindsay Haisley wrote: > Thus spake Jerry Amundson on Thu, Dec 16, 2004 at 08:55:13AM CST > > > On Wednesday 15 December 2004 05:26 pm, Sam Varshavchik wrote: > > > Jerry Amundson writes: > > > > On Wednesday 15 December 2004 06:14 am, Sam Varshavchik wrote: > > > >> Jerry Amundson writes: > > > >> > 250 Ok > > > >> > data > > > >> > 354 Feed me > > > >> > testing > > > >> > . > > > >> > > > > >> > ...and just sits there (thus the eventual timeout from > > > >> > courier). > > > >> > > > > >> > But, if I specifically end data with Enter.^V^M : > > > >> > .^M > > > >> > 250 Thanks > > > >> > > > > >> > So I still cannot determine if it's Courier's or Postini's > > > >> > issue? > > > >> > > > >> Courier terminates a message by sending .CRLF, so the above > > > >> doesn't really determine anything. > > > > > > > > Why would "addcr | TLS_VERIFYPEER=NONE couriertls > > > > -host=64.18.7.10 -port=25 -protocol=smtp" behave differently > > > > than a > > > > courieresmtp/couriertls delivery, which times out to the same > > > > IP? > > > > > > Right now, I resolve the MX record for psknet.com to 64.18.4.10. > > > > I was testing with postini.com > > Same same. All domains that use Postini's mail servers resolve all > their MX records to the same IP address, even though the mail server > fqdn is different in each case. I don't know how they do load > balancing.
Not quite, as they vary the MX amongst domains. Here's a sampling... Domain postini.com: Relay: postini.com.s8a1.psmtp.com, Priority: 100, Address: ::ffff:64.18.7.10 Relay: postini.com.s8a2.psmtp.com, Priority: 200, Address: ::ffff:64.18.7.10 Relay: postini.com.s8b1.psmtp.com, Priority: 300, Address: ::ffff:64.18.7.10 Relay: postini.com.s8b2.psmtp.com, Priority: 400, Address: ::ffff:64.18.7.10 Domain vicad.com: Relay: vicad.com.mail1.psmtp.com, Priority: 10, Address: ::ffff:64.18.4.10 Relay: vicad.com.mail2.psmtp.com, Priority: 1000, Address: ::ffff:64.18.4.10 Relay: vicad.com.mail3.psmtp.com, Priority: 1001, Address: ::ffff:64.18.4.10 Relay: vicad.com.mail4.psmtp.com, Priority: 1002, Address: ::ffff:64.18.4.10 Domain sjm.com: Relay: sjm.com.mail5.psmtp.com, Priority: 100, Address: ::ffff:64.18.5.10 Relay: sjm.com.mail6.psmtp.com, Priority: 200, Address: ::ffff:64.18.5.10 Relay: sjm.com.mail7.psmtp.com, Priority: 300, Address: ::ffff:64.18.5.10 Relay: sjm.com.mail8.psmtp.com, Priority: 400, Address: ::ffff:64.18.5.10 Domain emersonprocess.com: Relay: emersonprocess.com.s7a1.psmtp.com, Priority: 5, Address: ::ffff:64.18.6.10 Relay: emersonprocess.com.s7a2.psmtp.com, Priority: 6, Address: ::ffff:64.18.6.10 Relay: emersonprocess.com.s7b1.psmtp.com, Priority: 7, Address: ::ffff:64.18.6.10 Relay: emersonprocess.com.s7b2.psmtp.com, Priority: 8, Address: ::ffff:64.18.6.10 > Does anyone know if this problem can be traced to some sort of arcane > interaction between Courier and Postini's server, or are admins of > other MTAs that support TLS seeing the same thing? Recent googling turned up *nothing* for me on this... ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
