Every application seems to want the directory only and figure out what
to do from there. Exim is different, it wants the explicit file. Now it
works.
Thank you.
The error message might be more helpful if it mentioned what exactly is
"invalid" here.
I also found this code:
https://fossies.org/linux/exim/src/lookups/pgsql.c - Looks like the path
must contain a slash and a dot and then Exim takes that apart in a
certain way. This could simply be included in the message to give a hint
about the file name required.
-------- Ursprüngliche Nachricht --------
Von: Adam D. Barratt via Exim-users <exim-users@???>
Gesendet: Donnerstag, 17. September 2020, 23:23 MESZ
Betreff: [exim] Temporary internal error
On 17/09/2020 20:56, Yves Goergen via Exim-users wrote:
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.
On Thu, 2020-09-17 at 22:43 +0200, Yves Goergen via Exim-users wrote:
It does the same, just without the trailing slash. Note that this
path is a directory, not a file.
A UNIX domain socket is simply a special kind of file. The error
message refers to a filename, and the example in the documentation uses
a filename. So why are you passing it a directory name, rather than a
filename? :-)
Regards,
Adam
