Sam Varshavchik <[email protected]> wrote on 2010-Jun-08: > If Courier connects to an SMTP > server and the remote server supports STARTTLS (gmail's does), Courier will > negotiate an encrypted connection by default.
Does anyone know why "smtp.gmail.com" advertises STARTTLS, but the gmail MX servers do not? ---------------------------------------------- r...@mail:/# testmxlookup gmail.com Domain gmail.com: Relay: gmail-smtp-in.l.google.com, Priority: 5, Address: ::ffff:72.14.213.27 Relay: alt1.gmail-smtp-in.l.google.com, Priority: 10, Address: ::ffff:74.125.95.27 Relay: alt2.gmail-smtp-in.l.google.com, Priority: 20, Address: ::ffff:209.85.211.7 Relay: alt3.gmail-smtp-in.l.google.com, Priority: 30, Address: ::ffff:209.85.229.27 Relay: alt4.gmail-smtp-in.l.google.com, Priority: 40, Address: ::ffff:209.85.219.3 ---------------------------------------------- None of these advertise STARTTLS in response to an EHLO. So if I want to send mail securely to gmail.com, I need to put a entry in "esmtproutes" on each courier install forcing "smtp.gmail.com" for delivery to that domain? TIA Jeff Jansen ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
