search for: xapsd

...s. The plugin sends a notification over a socket to the daemon. The daemon then processes the request and returns a message to the plugin. The plugin reads the response then closes the socket and at that point, I?m running into an issue. The daemon reports the following: read unix /tmp/xapsd.sock->@: read: connection reset by peer In reading the Go language docs, it says that it will throw the first error it hits before the EOF from the socket. This led me to think that perhaps the plugin was not sending an EOF when closing the socket. I tried to write an EOF to the socket b...

I?m posting this here and will in a couple other places to see if anyone has any experience with this and knows what I can do. My setup is CentOS 6 with postfix, procmail and dovecot administered via Virtualmin. Postfix of course receives the email. Procmail uses it?s hooks to run the email through spam assassin and clamd. After than procmail hands it off to dovecot/deliver to drop it in the

...e daemon then processes the request and returns a message to the plugin. >> >> >> >> The plugin reads the response then closes the socket and at that point, I?m running into an issue. >> >> >> >> The daemon reports the following: read unix /tmp/xapsd.sock->@: read: connection reset by peer >> >> >> >> In reading the Go language docs, it says that it will throw the first error it hits before the EOF from the socket. This led me to think that perhaps the plugin was not sending an EOF when closing the socket. >>...

...on over a socket to the daemon. The daemon then processes the request and returns a message to the plugin. > > > > The plugin reads the response then closes the socket and at that point, I?m running into an issue. > > > > The daemon reports the following: read unix /tmp/xapsd.sock->@: read: connection reset by peer > > > > In reading the Go language docs, it says that it will throw the first error it hits before the EOF from the socket. This led me to think that perhaps the plugin was not sending an EOF when closing the socket. > > > > I t...