On Sun, 2012-09-02 at 19:03 -0700, Todd Lyons wrote: > On Sun, Sep 2, 2012 at 5:53 PM, Always Learning <[email protected]> wrote:
> > The reason I did not mention /var/run/clamav/clamd.sock was because > > the file was empty. > The file is a special kind of file, it's a "socket". clamd creates it > when it starts up and then anything that is running on the same > machine can connect to it kind of like a network socket, except that > it's ONLY local processes that may connect to it. > > If you do an 'ls -l' on that socket file, you'll see that it's type is > an "s" for socket. Yes I see now. > > Does one have to place the socket number in clamd.sock or will Exim or > > Clam do that automatically after the first AV check ? > You don't do anything to that file, just tell Exim to talk to clamd > through that socket. I understand your enthusiasm for that connection mechanism. Just metaphorically 'plug-in' and go. Thanks again. > The total budget at all receivers for solving senders' problems is $0. > If you want them to accept your mail and manage it the way you want, > send it the way the spec says to. --John Levine Wish M$ users would follow the specs rather than ignore 550 error codes and keep trying ad infinitum. -- Paul. England, EU. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
