Update letsyncrypt.js

Makes the hostname and email address used with registration configurable to something other than system.inet_addr. In case system has a different host name than the internet email domain.

added 1 deleted label

@rswindell This seems to address the issue(s) I was having regarding trying to run letsencrypt and it adding in an invalid domain for the system/host.

Possibly this should just switch both to use system.host_name instead of inet_addr. The idea that the system does not know it's own domain name seems highly flawed.

mentioned in issue #207 (closed)

@Deuce I tried that... and it still used the same host as inet_addr not the Hostname specified in sbbs.ini. (at least when run via jsexec, not sure if a timed event would have the same issue).

I have roughneckbbs.com on a separate server from synchronet... but synchronet is handling mx for the domain. The changes in this pr allowed it to be configured and work as such.

Right, the point is though that separate configuration shouldn't be required. The system should be able to use the web Hostname and be correct (see #207 (closed) for details). Currently that's not supported, but it should be simple to write a JS script or add more JS objects to get that information. You shouldn't need to configure the same thing (ie: web server public hostname) in multiple places (sbbs.ini and letsyncrypt.ini).

As more and more things generate URLs for the web server, this issue will just get worse.

Updated and committed as d4bdf4ff

closed