Kārlis Repsons a écrit :
> Hi,
> maildrop seems to reject any efforts on my part, take a look at this:
>
> Tried using maildrop with postfix as described in the second part of [1], but
> it failed. strace showed me:
> "connect(3, {sa_family=AF_FILE,
> path="/var/lib/courier/authdaemon/socket"...},
> 110) = -1 ENOENT (No such file
> or directory)".
>
> Then I tried to copy another socket with name "socket", but it
> failed with:
> "connect(3, {sa_family=AF_FILE,
> path="/var/lib/courier/authdaemon/socket"...}, 110) = -1 ECONNREFUSED
> (Connection refused)".
>
> I'm confused about this, what is wrong? Apparently sockets can't be created
> as
> easy as pipes (excuse me, what commandline tool cares for that?).
> Maybe someone in here had to solve this problem before?
>
sockets are communication end points. a server creates a socket where
clients can connect to and talk to the server...
Your maildrop needs to contact the courier authdaemon server. Make sure,
authdaemon is running and correctly configured. if you don't need it,
you'll need to rebuild maildrop without authlib support.
anyway, this is not postfix related. maildrop is part of the courier
suit. you'll get more help on the courier-maildrop mailing list.
>
> [1] http://www.postfix.org/MAILDROP_README.html
