Re: Error handler that asks user to report crash
Posted: Tue May 09, 2017 8:52 pm
Apparently some time in the last few years, major ISPs started blocking outgoing connections on port 25 from residential accounts / dynamic IPs.
https://www.xfinity.com/support/interne ... supported/
This is probably a bit silly since there's nothing inherently insecure about port 25; server could easily allow TLS upgrade on that port, or accept unencrypted SMTP on a different port. Anyway, there are email services that provide an alternate port for this, or choose not to enforce TLS upgrade on 587 or some other port. Two that look promising are mailgun.com and smtp2go.com. Their free service is limited, but don't look like they require a credit card and should be enough if your game's not throwing a crazy amount of different errors.
Unfortunately gmail only allows unencrypted connections over port 25 as far as I can tell. It looks like maybe it can be reconfigured for "G Suite" (formerly Google Apps), but I haven't tried it.
I'm finally convinced #363 (some kind of API on top of openssl / whatever ships with Windows) is a good idea, as the world seems to be moving in the general direction of trying to enforce encryption everywhere even when unnecessary.
https://www.xfinity.com/support/interne ... supported/
This is probably a bit silly since there's nothing inherently insecure about port 25; server could easily allow TLS upgrade on that port, or accept unencrypted SMTP on a different port. Anyway, there are email services that provide an alternate port for this, or choose not to enforce TLS upgrade on 587 or some other port. Two that look promising are mailgun.com and smtp2go.com. Their free service is limited, but don't look like they require a credit card and should be enough if your game's not throwing a crazy amount of different errors.
Unfortunately gmail only allows unencrypted connections over port 25 as far as I can tell. It looks like maybe it can be reconfigured for "G Suite" (formerly Google Apps), but I haven't tried it.
I'm finally convinced #363 (some kind of API on top of openssl / whatever ships with Windows) is a good idea, as the world seems to be moving in the general direction of trying to enforce encryption everywhere even when unnecessary.