Hi Steve,
It returns "No packages found matching mailscanner."
I manually removed the remaining elements the other day though. I don't
know if this has cause dpkg to return nothing. Sorry, my experience is
with RPM, not DEB.
--
MailScanner when removed leaves script in cron.daily
https://launch
NOTE: I found yesterday also that as Cyrus-IMAP requires the socket to
be located in /var/run/saslauthd/ , and would seem that you can not tell
Cyrus-IMAP where to look for the socket (I am yet to 100% confirm this),
that I had to make a symlink to the location where my socket was. Also
as on reboo
Public bug reported:
Binary package hint: mailscanner
OS: Ubuntu 6.06 Server LTS (32bit)
While building a spamwall, at one point I installed MailScanner, but
later removed it. I noticed that I'm getting errors daily saying that
MailScanner cron.daily failed.
Various elements of MailScanner have
Public bug reported:
Binary package hint: sasl2-bin
Package: sasl2-bin
OS: Ubuntu Server 6.06 LTS
All Updates Applied: Yes
Problem:
Due to having to move the Cyrus-SASL mux socket to another directory, to
allow postfix access to it, I later found that the init script at
/etc/init.d/saslauthd co
