I'm having a problem with our CFMX spooler. This isn't a problem of e-mails being tossed into the Undelivr folder, and we don't have the money to afford $500 for such a small problem.
Today is the second time this has happened since I've worked here. The first time was exactly 7 days ago. E-mails seem to not be getting spooled and there are no error messages regarding any failures or successes. The first time this happened we had some 40 or 50 e-mails just sitting in the spool folder and the server had been running for 99 days. So we rebooted the server and the spool folder cleared up just fine. This time the server was only running 7 days and there were another bunch of e-mails in the spool folder. So I rebooted it and after a few minutes the spool folder cleared up.
The problem is, we have some anal clients who want to get their order notifications instantly. If they see their orders showing up in their e-commerce backends, they want to see the e-mails in their inbox. So I have to go in and fix the spool so they get their e-mails. I'd like to know if there's some perminant fix to this spool problem.
Presently the spool runs every 15 seconds. I'm debating moving that back to every 60 seconds, but I'd like to get your feedback as to what would be the best move. Is this a known bug in MX6.1? or is this something undocumented that has to do with the spool running too slow and tripping over itself after 15 seconds?
Steve Kiehl
Web Page Designer - Nanovox Productions
Fantasy Artist - Zeadi
Today is the second time this has happened since I've worked here. The first time was exactly 7 days ago. E-mails seem to not be getting spooled and there are no error messages regarding any failures or successes. The first time this happened we had some 40 or 50 e-mails just sitting in the spool folder and the server had been running for 99 days. So we rebooted the server and the spool folder cleared up just fine. This time the server was only running 7 days and there were another bunch of e-mails in the spool folder. So I rebooted it and after a few minutes the spool folder cleared up.
The problem is, we have some anal clients who want to get their order notifications instantly. If they see their orders showing up in their e-commerce backends, they want to see the e-mails in their inbox. So I have to go in and fix the spool so they get their e-mails. I'd like to know if there's some perminant fix to this spool problem.
Presently the spool runs every 15 seconds. I'm debating moving that back to every 60 seconds, but I'd like to get your feedback as to what would be the best move. Is this a known bug in MX6.1? or is this something undocumented that has to do with the spool running too slow and tripping over itself after 15 seconds?
Steve Kiehl
Web Page Designer - Nanovox Productions
Fantasy Artist - Zeadi