Postie & Register.com

this is the config page that comes out:

Postie Configuration Test
Postie Version: 1.8.31
Wordpress Version: 4.7.3
PHP Version: 5.6.17-pl0-gentoo
OS: Linux atl4vux143 4.4.5-hardened-r2 #1 SMP Fri Oct 21 20:48:01 EDT 2016 x86_64
POSTIE_DEBUG: On
Error log:
TMP dir: /tmp/
Postie is in /data/49/4/162/115/4814278/user/5700421/htdocs/wp-content/plugins/postie/
cURL version: 7.39.0
Cron: On
Alternate Cron: Off
Clock

This shows what time it would be if you posted right now

Wordpress timezone: (-5)
Current time: 2017-03-07 11:27:13
Current time (gmt): 2017-03-07 16:27:13
Postie time correction: -5
Post time: 2017-03-07 11:27:08
Encoding

default_charset: UTF-8
DB_CHARSET: utf8mb4
DB_COLLATE: database default
WordPress encoding: UTF-8
Postie encoding: UTF-8
Connect to Mail Host

Postie connection: sockets
Postie protocol: pop3
Postie server: [email protected]
Postie port: 110
Connecting via Socket
Socket: [email protected]:110

Warning: stream_socket_client(): php_network_getaddresses: getaddrinfo failed: Name or service not known in /data/49/4/162/115/4814278/user/5700421/htdocs/wp-content/plugins/postie/lib/pSocketConnection.php on line 37

Warning: stream_socket_client(): unable to connect to [email protected]:110 (php_network_getaddresses: getaddrinfo failed: Name or service not known) in /data/49/4/162/115/4814278/user/5700421/htdocs/wp-content/plugins/postie/lib/pSocketConnection.php on line 37
Socket error: 0 – php_network_getaddresses: getaddrinfo failed: Name or service not known
Unable to connect. The server said:
There was an error connecting to the server php_network_getaddresses: getaddrinfo failed: Name or service not known

Hi,

Thanks, I got that address when I telnet to my mail server. However when I pu my mail server in as mail.doilove.org on the Postie settings and test the connection I get this error message:

An error occurred.

Sorry, the page you are looking for is currently unavailable.
Please try again later.

If you are the system administrator of this resource then you should check the error log for details.

Faithfully yours, OpenResty.

Yes, this is the Error

Syntax: error_log file [level];
Default:
error_log logs/error.log error;
Context: main, http, mail, stream, server, location
Configures logging. Several logs can be specified on the same level (1.5.2). If on the main configuration level writing a log to a file is not explicitly defined, the default file will be used.

The first parameter defines a file that will store the log. The special value stderr selects the standard error file. Logging to syslog can be configured by specifying the “syslog:” prefix. Logging to a cyclic memory buffer can be configured by specifying the “memory:” prefix and buffer size, and is generally used for debugging (1.7.11).

The second parameter determines the level of logging, and can be one of the following: debug, info, notice, warn, error, crit, alert, or emerg. Log levels above are listed in the order of increasing severity. Setting a certain log level will cause all messages of the specified and more severe log levels to be logged. For example, the default level error will cause error, crit, alert, and emerg messages to be logged. If this parameter is omitted then error is used.

For debug logging to work, nginx needs to be built with –with-debug, see “A debugging log”.
The directive can be specified on the stream level starting from version 1.7.11, and on the mail level starting from version 1.9.0.

My site is on a hosted server. I haven’t configured any error logging.