Re: [qmailtoaster] Re: /tmp/clamd.socket is in use by another process was Re: supervise: fatal: unable to start log/run: file does not exist
Monday, June 30, 2014, 6:03:11 PM, Eric wrote: Yeah, it's trying to run from both supervise and init.d. That's what I thought - the question is, how do I fix this without accidentally making things worse? (Well, the *other* question is, what caused the problem in the first place, but at the moment I'm more interested in solving it.) Which clamd version is installed? [root@qmail ~]# yum list clamd Loaded plugins: fastestmirror, priorities, refresh-packagekit Loading mirror speeds from cached hostfile * base: less.cogeco.net * extras: less.cogeco.net * qmailtoaster-current: mirror2.qmailtoaster.com * qmailtoaster-current-nodist: mirror2.qmailtoaster.com * remi: rpms.famillecollet.com * rpmforge: ftp.heanet.ie * updates: mirror.science.uottawa.ca 162 packages excluded due to repository priority protections Available Packages clamd.x86_64 0.98.4-1.el6.rf rpmforge Okay, that was odd. One clamd package available but none installed. So, try a slight variation... [root@qmail ~]# yum list clam* Loaded plugins: fastestmirror, priorities, refresh-packagekit Loading mirror speeds from cached hostfile * base: less.cogeco.net * extras: less.cogeco.net * qmailtoaster-current: mirror2.qmailtoaster.com * qmailtoaster-current-nodist: mirror2.qmailtoaster.com * remi: rpms.famillecollet.com * rpmforge: ftp.heanet.ie * updates: mirror.science.uottawa.ca 162 packages excluded due to repository priority protections Installed Packages clamav.x86_64 0.98.4-0.qt.el6@qmailtoaster-testing Available Packages clamav-db.x86_640.98.4-1.el6.rfrpmforge clamav-devel.x86_64 0.98.4-1.el6.rfrpmforge clamav-milter.x86_640.98.4-1.el6.rfrpmforge clamd.x86_640.98.4-1.el6.rfrpmforge clamtk.noarch 4.25-1.el6.rf rpmforge Okay, looks like the package is actually clamav not clamd and I have version 0.98.4-0 installed. As for my qmailtoaster itself: Installed Packages qmailtoaster-release.noarch 2.0-1.qt.nodist installed Installed Packages qmailtoaster-util.noarch 2.0-1.qt.nodist @qmailtoaster-current-nodist qmailtoaster-testing is disabled in my repos and qmailtoaster-current is enabled (and set to a slightly higher priority than the testing repo back when I changed over from testing to current, just in case that made any difference). -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Spam Blocked due to a client with a virus/trojan.
Hi folks, Not sure if there is a cure for this but I will ask. Very recently a customer got a virus or trojan on their machine which spammed using her account. This caused my mail server to be spam blocked. Not good but not permanent. So... 1. Can we throttle the account? 2. Making the max recipients a smaller number does not seem to slow down this sort of thing. Other alternatives? 3. How do we see a high volume from a single client and stop accepting emails from that address? 4. Is there a way of monitoring the client send and if it exceeds a set limit per minute change the client password and disconnect them? Appreciate anyone else having any thoughts or methods? -- best wishes Tony White - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: /tmp/clamd.socket is in use by another process was Re: supervise: fatal: unable to start log/run: file does not exist
Sorry about the clamd/clamav confusion. The package name is clamav. You have the latest version from .qt., but I'm curious as to how you got the testing version, if that repo is disabled (as it should be now in most setups). That's where the the problem lies though. The testing version is the first version to include the init.d file for clamd instead of the supervise setup. I thought that rpm would remove the old supervise run file since it's not part of the package any more, but it appears I'll need to put some code in the rpm spec file to do that 'manually'. I think the best fix for you at this point will be to simply get rid of the /var/qmail/supervise/clamd/ directory. You might move it to /root/ as a backup rather than simply deleting it. It'd be safest to do this with qmail/supervise stopped, so that supervise doesn't get confused. You might then need to service clamd start to get clamd running before starting qmail back up. That should fix it for you. Thanks for testing this out, even though it was apparently inadvertent. We all appreciate your help. -- -Eric 'shubes' On 07/02/2014 07:09 AM, Diana Calder wrote: Monday, June 30, 2014, 6:03:11 PM, Eric wrote: Yeah, it's trying to run from both supervise and init.d. That's what I thought - the question is, how do I fix this without accidentally making things worse? (Well, the *other* question is, what caused the problem in the first place, but at the moment I'm more interested in solving it.) Which clamd version is installed? [root@qmail ~]# yum list clamd Loaded plugins: fastestmirror, priorities, refresh-packagekit Loading mirror speeds from cached hostfile * base: less.cogeco.net * extras: less.cogeco.net * qmailtoaster-current: mirror2.qmailtoaster.com * qmailtoaster-current-nodist: mirror2.qmailtoaster.com * remi: rpms.famillecollet.com * rpmforge: ftp.heanet.ie * updates: mirror.science.uottawa.ca 162 packages excluded due to repository priority protections Available Packages clamd.x86_64 0.98.4-1.el6.rf rpmforge Okay, that was odd. One clamd package available but none installed. So, try a slight variation... [root@qmail ~]# yum list clam* Loaded plugins: fastestmirror, priorities, refresh-packagekit Loading mirror speeds from cached hostfile * base: less.cogeco.net * extras: less.cogeco.net * qmailtoaster-current: mirror2.qmailtoaster.com * qmailtoaster-current-nodist: mirror2.qmailtoaster.com * remi: rpms.famillecollet.com * rpmforge: ftp.heanet.ie * updates: mirror.science.uottawa.ca 162 packages excluded due to repository priority protections Installed Packages clamav.x86_64 0.98.4-0.qt.el6@qmailtoaster-testing Available Packages clamav-db.x86_640.98.4-1.el6.rfrpmforge clamav-devel.x86_64 0.98.4-1.el6.rfrpmforge clamav-milter.x86_640.98.4-1.el6.rfrpmforge clamd.x86_640.98.4-1.el6.rfrpmforge clamtk.noarch 4.25-1.el6.rf rpmforge Okay, looks like the package is actually clamav not clamd and I have version 0.98.4-0 installed. As for my qmailtoaster itself: Installed Packages qmailtoaster-release.noarch 2.0-1.qt.nodist installed Installed Packages qmailtoaster-util.noarch 2.0-1.qt.nodist @qmailtoaster-current-nodist qmailtoaster-testing is disabled in my repos and qmailtoaster-current is enabled (and set to a slightly higher priority than the testing repo back when I changed over from testing to current, just in case that made any difference). - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: Spam Blocked due to a client with a virus/trojan.
On 07/02/2014 07:32 AM, Tony White wrote: Hi folks, Not sure if there is a cure for this but I will ask. Very recently a customer got a virus or trojan on their machine which spammed using her account. This caused my mail server to be spam blocked. Not good but not permanent. So... 1. Can we throttle the account? Not at this point. I've spec'd out a patch to qmail-remote that will add a throttle to it, but it remains to be coded and implemented. I think this will be the best solution to this problem. I'll see about making this a priority, but at this point I wouldn't expect to see anything being done with it before the end of the year. If someone or several someones were to sponsor this development, that would accelerate things. 2. Making the max recipients a smaller number does not seem to slow down this sort of thing. Other alternatives? Not that I'm aware of. 3. How do we see a high volume from a single client and stop accepting emails from that address? The throttle will/would do that. 4. Is there a way of monitoring the client send and if it exceeds a set limit per minute change the client password and disconnect them? IIRC, someone has written a simple script to detect when this happens. If so, please chime in. We could use an interim solution that would help with this. Appreciate anyone else having any thoughts or methods? Ditto. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
