Probably. Never looked at doing it that way. You still have to parse some
text either way. My method seems to work just fine for me and never looked
So if I base the queue count by adding up the files that match
“/var/surgemail/work/*/*.idx” while I be missing something?
*From:*Lyle Giese [mailto:firstname.lastname@example.org]
*Sent:* Saturday, August 10, 2013 7:49 AM
*Subject:* Re: [SurgeMail List] re: Reload work directory
I grab the output of
and grab the numbers on the lines 'In Memory que' and 'On Disk que',
add them to together and send alerts based on a threshold for that number
that works for my server.
I mentioned the other day that an account was hacked and was used to
send alot of spam. This method was my first alert to the problem.
LCR Computer Services, Inc.
On 08/09/13 22:29, Frank Bulk wrote:
You may want to have something watch your queues a bit more
closely if systems currently allow up to 200K messages to build
up. At our site we consider it a “bad day” if more than a few
hundred spam messages are queued/delayed for delivery.
*Sent:* Thursday, August 08, 2013 5:10 PM
*Subject:* [SurgeMail List] re: Reload work directory
I think it will probably find them eventually anyway, but to be sure:
And restart, that should force it to recheck.
If it still fails, make sure you placed them in the right matching
work sub folder that they came from.
somebody got hold of a mail account and password and used our
After stopping the server and changing the password I found
mails in the work directory that had not been sent. I moved
and restarted the server. Everything runs fine.
After that I found 153 non Spam mails between the 200.000
mails, I moved
these files back in the work directory (*.idx and *.itm).
However, despite restarting surgemail, these 153 are not sent.
How do get surgemail to work on these?