One step further: I added another slash at the database connection and
just left the password empty. Now I get this output:
PGSQL new connection: socket=/var/run/postgresql/ database=dfctl
user=mailreader
lookup deferred: PGSQL invalid filename for socket: /var/run/postgresql/
The first line looks as expected now, and the second, too. But why can't
Exim accept that path if all other applications can?
-------- Ursprüngliche Nachricht --------
Von: Yves Goergen via Exim-users <exim-users@???>
Gesendet: Donnerstag, 17. September 2020, 21:56 MESZ
Betreff: [exim] Temporary internal error
Hm, this prints more details, among others:
PGSQL new connection: socket=/var/run/postgresql database=) user=dfctl
lookup deferred: PGSQL invalid filename for socket: /var/run/postgresql
I'm not sure what's exactly invalid here. But it's not what I configured
either. This is the relevant config:
PGSQL_HOST = (/var/run/postgresql/)
PGSQL_USER = mailreader
PGSQL_DB = dfctl
hide pgsql_servers = "PGSQL_HOST/PGSQL_DB/PGSQL_USER"
Somehow Exim got confused with the database connection parts. The
parenthesis syntax was explained in the documentation, to avoid
confusion with all those slashes in there. Doesn't seem to work, it got
confused.
How should I configure a PostgreSQL connection using a local socket and
no password in Exim?
The socket path works fine in Dovecot, exactly as shown, with leading
and trailing slash.
-------- Ursprüngliche Nachricht --------
Von: Jeremy Harris via Exim-users <exim-users@???>
Gesendet: Donnerstag, 17. September 2020, 21:42 MESZ
Betreff: [exim] Temporary internal error
On 17/09/2020 20:32, Yves Goergen via Exim-users wrote:
exim -bt demo@???
exim -d -bt demo@???
