News for hackers. Stuff that matters.

A comment on Google Fiber now allows servers for non-commercial use. Parent comment

Re:Google Fiber now allows servers for non-commercial use by doctorohhnoes on Monday October 14, 2013 @05:55PM (#6549889)
Come to think of it, I've never looked at inbound stuff. You'd think outbound would be where all the spam problems come from, though.
[ Parent | on HN ]
Re:Google Fiber now allows servers for non-commercial use by pyre on Monday October 14, 2013 @06:18PM (#6550005)
> You'd think outbound would be where all the spam problems come from, though.

They block port 25 to prevent open relays on their network (i.e. someone sends a forged email, the SMTP server does no authentication, and just forwards it on to the destination).

[ Parent | on HN ]
Re:Google Fiber now allows servers for non-commercial use by sliverstorm on Monday October 14, 2013 @06:01PM (#6549913)
If you block 25 outbound, people's mail clients (Outlook, Thunderbird, etc) could not deliver mail to servers that don't run SSL or TLS (465, 587)
[ Parent | on HN ]
Re:Google Fiber now allows servers for non-commercial use by werid on Monday October 14, 2013 @06:03PM (#6549927)
Lots of ISPs does this. They require you to relay via their SMTP-server.
[ Parent | on HN ]
Re:Google Fiber now allows servers for non-commercial use by ckuehl on Monday October 14, 2013 @06:46PM (#6550122)
Ideally you would use port 587, which is the designated port for mail submission. See RFC 2476 [1].

This requires that your mail provider supports that port, of course, which is unfortunately not always the case.

[1] http://www.ietf.org/rfc/rfc2476.txt

[ Parent | on HN ]
Re:Google Fiber now allows servers for non-commercial use by daigoba66 on Monday October 14, 2013 @06:34PM (#6550080)
Used to have Bellsouth DSL, and they did this. SMTP/TLS on a different port worked though. But obviously you couldn't run your own e-mail server.
[ Parent | on HN ]