public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Technical imap mail question
Date: Thu, 15 Oct 2015 23:01:16 +0100	[thread overview]
Message-ID: <201510152301.26906.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20151015100422.55984dd8@a6>

[-- Attachment #1: Type: Text/Plain, Size: 1768 bytes --]

On Thursday 15 Oct 2015 18:04:22 walt wrote:
> My ISP recently started offering imap email service in addition to
> the pop3/smtp servers they've always had, so I decided to try it.
> 
> I was surprised to see that they recommend using a different smtp
> server name when setting up my mail client, and they even offer the
> option of using port 587 instead of 465 if I prefer it.
> 
> Why would I use a different smtp server if I'm now using imap?  I use
> smtp to send mail, and imap to read it, right?  Why not use the same
> smtp server in either case?
> 
> (The different server names actually resolve to the same IP address, so
> the distinction seems to be more theoretical than real, but the theory
> is what puzzles me.)
> 
> Thanks.

Port 587 is for TLS and is the proper port to be used by MSAs as per RFC6409.

Port 467 on the other hand is for SMTPS:  vanilla SMTP at the application 
level, but the communication to the server is still secured at the transport 
layer with SSL.  This was an IANA attempt to provide a port for secure email 
communication pre-STARTTLS days.  Today I think may be used for other 
purposes, but I am not sure if it is TCP or UDP streaming.

Port 25 (outgoing) is blocked by most domestic ISPs to guard against the 
millions of pawned botnets out there filling out inboxes with spam.

The question about a different SMTP server might have something to do with 
your ISP adding a new SMTP mailserver to their farm and configuring it 
properly this time as per RFC6409.  Although as Alan said, they probably 
rolled out whatever the chosen ISP package software vendor provided for them 
without knowing much about it, or why it is configured the way it is 
configured.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2015-10-15 22:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 17:04 [gentoo-user] Technical imap mail question walt
2015-10-15 17:55 ` Alan McKinnon
2015-10-15 17:59 ` J. Roeleveld
2015-10-15 18:00 ` Michael Orlitzky
2015-10-15 22:01   ` Bill Kenworthy
2015-10-15 22:01 ` Mick [this message]
2015-10-16  2:29   ` Terry Z.
2015-10-16  5:14   ` Tuomo Hartikainen
2015-10-16 11:15     ` Mick
2015-10-16 14:52 ` [gentoo-user] " Grant Edwards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201510152301.26906.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox