[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ingress SMTP
- Subject: ingress SMTP
- From: cboyd at gizmopartners.com (Chris Boyd)
- Date: Wed, 3 Sep 2008 16:53:28 -0500
- In-reply-to: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAADeoNCUK2DtS7H9VOzxN7YFAQAAAAA=@iname.com>
- References: <[email protected]> <[email protected]> <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAADeoNCUK2DtS7H9VOzxN7YFAQAAAAA=@iname.com>
On Sep 3, 2008, at 4:36 PM, Frank Bulk wrote:
> I would like to point my customers to port 587, but that kind of
> configuration is still in its infancy.
We're a small managed services provider, and we started doing
authenticated SMTP with TLS on port 587 six years ago. It's at least
in kindergarten :-)
Once we explain the advantages, our customers love it since their
email "just works" pretty much wherever they go.
As a former manager for a small resnet, blocking port 25 outbound is A
Good Thing. Cut abuse email down by a huge factor.
--Chris