Dear Teodor Micu
thanks for looking at my patch and thanks for your mail, could you please give
me an example how the && sequences may fail as I've done some tests with it and
it seems it catches all normal configurations, even when a user if specified
for a network milter socket, and the alternative implementation here seems to
consist of stacked if-clauses.
Regarding the splitting of MILTERSOCKET into MILTERTYPE and MILTERSOCKET I'm
currently little bit undecided as the manpage of amavisd-milter is written like
this:
-s socket
Communication socket between sendmail and amavisd-milter (default
/var/lib/amavis/amavisd-milter.sock). The protocol spoken over this socket is
MILTER
(Mail FILTER). It must agree with the INPUT_MAIL_FILTER entry in
sendmail.mc
The socket should be in "proto:address" format:
· {unix|local}:/path/to/file - A named pipe.
· inet:port@{hostname|ip-address} - An IPV4 socket.
· inet6:port@{hostname|ip-address} - An IPV6 socket.
Splitting the MILTERSOCKET variable into two params may irritate users looking
into the documentation more than it helps avoiding potential problems, maybe we
should bring this question to debian-devel to get a broader audience for this
discussion?
Kind regards
Harald Jenny
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
