On 14/10/11 15:51, Stan Hoeppner wrote: > On the public internet you can't force remote SMTP servers to use > encryption when connecting to your server, because very few, if any, > public SMTP servers implement outbound encryption in this way. Most > send in plain text, and always have. For instance, what I'm typing > right now will arrive at the Postfix list server. My Postfix smtp > server doesn't support transmitting outbound mail with encryption (yours > probably doesn't either). If the list server did require encryption I > wouldn't be able to send my reply. This is what RFC 2487 is getting at > here.
Right, I get this part, it's just the last sentence that is confusing to me. > What "dedicated servers" means in this context are SMTPD servers within > an organization dedicated to a specific task, in this case almost always > relay submission. These are the SMTPD servers that accept relay mail > from your users' MUAs, such as Thunderbird and Outlook Express. Such > clients all support outbound encryption. If you've ever used an ISP > mail account and setup your "outbound SMTP server settings" then you > should understand encryption in this context. > > Configuring the 'submission' service or '587' service in your Postfix > master.cf would create the "dedicated server" mentioned above. Right, that makes sense, but seems to clash with the conventional definition for "dedicated server" (from wikipedia): > A dedicated hosting service, dedicated server, or managed hosting > service is a type of Internet hosting in which the client leases an > entire server not shared with anyone. This is what I (and I think most people) understand "dedicated server" to mean. There must be a better term for this that is less confusing. Peter
