[102981] in North American Network Operators' Group
Re: Customer-facing ACLs
daemon@ATHENA.MIT.EDU (JC Dill)
Tue Mar 11 02:27:00 2008
Date: Mon, 10 Mar 2008 23:25:59 -0700
From: JC Dill <lists05@equinephotoart.com>
CC: nanog@merit.edu
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAABR1I6GGb50R7m9DdTtR+jPAQAAAAA=@iname.com>
Errors-To: owner-nanog@merit.edu
Doesn't anyone RTFM before posting anymore?
http://mail.google.com/support/bin/answer.py?hl=en&answer=13287
# Configure your client to match the settings below:
Incoming Mail (POP3) Server - requires SSL: pop.gmail.com
Use SSL: Yes
Port: 995
Outgoing Mail (SMTP) Server - requires TLS: smtp.gmail.com (use
authentication)
Use Authentication: Yes
Use STARTTLS: Yes (some clients call this SSL)
Port: 465 or 587
There is no need to use smtp on port 25 with gmail. configure the
client according to gmail's instructions and use 465 or 587.
jc
Frank Bulk - iNAME wrote:
> Those using Google for SMTP can still use their ISP's SMTP servers for
> outbound....
>
> Frank
>
> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Ang
> Kah Yik
> Sent: Monday, March 10, 2008 7:40 PM
> To: Andy Dills
> Cc: nanog@merit.edu
> Subject: Re: Customer-facing ACLs
>
>
> Hi Andy (and all who responded),
>
> Thanks for the heads-up on the redirection on SMTP traffic. I've yet to
> see an implementation of it but I agree that it's a possible solution.
>
> As for the issue I raised previously, perhaps corporate users isn't a
> good example but what about users of email services such as Gmail and
> the like?
