* On 09 Nov 2014, DaleKelly wrote: > On 11/09/2014 07:42 PM, DaleKelly wrote: > >got it to work without SSL/TLS in my smtp_url > > the caveats might have been > installing everyone related before ubuntu version > adding "" around the string for smtp_url > no SSL/TSL, and using port 80 instead of 25
I would not advise authenticating without SSL (encryption). Your login credentials have been exposed in cleartext. Port 465 is TLS/SSL with encryption right off the bat, no negotation. Port 587 is usually negotiated TLS (STARTTLS), but this can be offered over port 25. There is no reasonable explanation for SMTP working over port 80. It does appear that your server provides SMTP on port 80, so... ok then. But this is clearly a wacky thing specific to your provider. Virtually nobody does this. It's not normal. I guess they do it to allow customers to relay mail through firewalls that allow port 80 (HTTP) but block SMTP (or think they do). That said, it's clear that they also honor port 465: [1220/1]$ openssl s_client -connect smtpout.secureserver.net:465 -quiet depth=2 C = US, O = "Starfield Technologies, Inc.", OU = Starfield Class 2 Certification Authority verify return:1 depth=1 C = US, ST = Arizona, L = Scottsdale, O = "Starfield Technologies, Inc.", OU = http://certificates.starfieldtech.com/repository, CN = Starfield Secure Certification Authority, serialNumber = 10688435 verify return:1 depth=0 C = US, ST = AZ, L = Scottsdale, O = "Special Domain Services, Inc.", CN = smtpout.secureserver.net verify return:1 220 p3plsmtpa07-01.prod.phx3.secureserver.net ESMTP quit 221 p3plsmtpa07-01.prod.phx3.secureserver.net closing connection And port 25: [1224/130]$ telnet smtpout.secureserver.net 25 Trying 173.201.192.229... Connected to smtpout.secureserver.net. Escape character is '^]'. 220 p3plsmtpa07-09.prod.phx3.secureserver.net ESMTP starttls 500 command unrecognized quit 221 p3plsmtpa07-09.prod.phx3.secureserver.net closing connection Since port 25 doesn't negotiate TLS, you might continue trying to get 465 to work. I think you're having problems with the SASL authentication here, not with the connectivity itself. Debug output might help us figure it out. -- David Champion • [email protected]
