On Friday 25 March 2011 12:34:37 /dev/rob0 wrote: > 1. Why did you switch from ssmtp? It's possible, even likely, that > your needs would be better served by a null SMTP client, rather > than a MTA such as Postfix. >
Like you said this enables you to use a single client to access your mail. If you have a tendency to migrate to new systems and hardware abstactly it becomes annoying. Like leaving your mail on the pop server so you can read at another location etc. The benefits of using an MTA that will work with imap and offload your mail from a remote popserver are tremendous. Understanding the archetecture is a steep slope. This is why I wanted a simple implimentation working first > 2. smtp.frontier.com has submission servers on ports 25, 465 (smtps), > and 587. Ports 25 and 587 do not appear to support STARTTLS, so if > you desire encryption, your only choice is the deprecated smtps > subprotocol. Postfix does not implement smtps as a client, only as > a server. There is a workaround using stunnel: > http://www.postfix.org/TLS_README.html#client_smtps > if you use 465 there will be a message in the log telling you to use 587. I think the only thing frontier is enforcing is sasl so I guess 25 should work and be the simplest. At any rate this will send me back to that rather long message from my ISP stating I'm not identifying myself. From my own server experience when in this predicament I up the verbosity of whatever app and try to provoke more information. > BTW, I did not try to decode your AUTH string shown upthread, but if > that was the actual string you used at smtp.frontier.com, you must > change your password now. AUTH PLAIN has no security; it merely > obscures the username and password. yeah stupid .... something I would not have done if I was not swimming in the rapids :)
