[146115] in North American Network Operators' Group
Re: Outgoing SMTP Servers
daemon@ATHENA.MIT.EDU (Bill Stewart)
Thu Nov 3 17:16:39 2011
In-Reply-To: <F05D77A9631CAE4097F7B69095F1B06F59722E48@EX02.drtel.lan>
Date: Thu, 3 Nov 2011 14:15:19 -0700
From: Bill Stewart <nonobvious@gmail.com>
To: Brian Johnson <bjohnson@drtel.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Mon, Oct 31, 2011 at 6:23 AM, Brian Johnson <bjohnson@drtel.com> wrote:
> For clarity it's really bad for ISPs to block ports other than 25 for the=
purposes of mail flow control... correct?
Yes, correct. If you're using another mail submission port, you're
connecting to a mail service that has the responsibility not to let
spam escape, and your ISP has done its job of stopping point-source
pollution.
>Bill>I've got a strong preference for ISPs to run a
>Bill>Block-25-by-default/Enable-when-asked. =A0[...]
> This is, of course, exactly why this blocking is done.
It looks like you're missing half my point, which is the Enable-when-asked =
part.
There are users who are perfectly legitimately running MTAs at home,
whether for reliability or privacy (e.g. so they can run SMTP-over-TLS
end-to-end) or just simplicity, and ISPs shouldn't be blocking them
(unless they're spammers, of course.)
> My take on this is that it IS best practice to have users use the submiss=
ion port (587) for mail submission from the MUA to an MTA.
If you're running an MTA service, then yes. If you're running a
transport service, then not necessarily.
--=20
----
=A0 =A0 =A0 =A0 =A0 =A0=A0 Thanks;=A0 =A0=A0 Bill
Note that this isn't my regular email account - It's still experimental so =
far.
And Google probably logs and indexes everything you send it.
