[TriLUG] OT: ATT UVerse internet access
bak
bak at picklefactory.org
Wed Mar 30 18:40:49 EDT 2011
Indeed!
In dealing with your company, though, it's not necessarily the case that
587 is insecure, however. For example, my MTA (postfix) supports
STARTTLS on 587, so the encryption happens after the TCP handshake
instead of before.
--bak
On 3/30/11 5:44 PM, Michael Hrivnak wrote:
> Another vote for the submission port. This is why it exists.
> Hopefully you can use the SSL flavored one (port 465). If your
> employer really wants you to send email through their MTA, they should
> provide you with the submission port.
>
> Michael
>
> On Wed, Mar 30, 2011 at 3:29 PM, bak <bak at picklefactory.org> wrote:
>> On 3/30/11 3:10 PM, Chris Merrill wrote:
>>> For anyone else considering the service - there is one "gotcha" to look out for. AT&T
>>> blocks outgoing connections to port 25. I need to send work e-mails through our server,
>>> not theirs, so this is a critical issue for me.
>>
>> I got around this by using the 'submission' port. Modern UNIX MTAs have
>> this turned on by default. It is basically just
>> SMTP-with-authentication-by-default; no relaying. The well-known port is
>> 587. See RFC2476.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <http://www.trilug.org/pipermail/trilug/attachments/20110330/cafb1f5b/attachment.pgp>
More information about the TriLUG
mailing list