Comments
-
Greg Hurrell
Ok, I've started work on this now.
Currently have a background worker daemon that wakes up every 15 seconds to see if there's any work to do; in this way we just bootstrap Rails once rather than every time we run.
The first job of this worker daemon is going to be to check for handling incoming email, but I plan to use the same daemon to handle all background processing tasks (don't want multiple daemons due to the memory footprint).
-
Greg Hurrell
-
Greg Hurrell
As one example of this can be done, see how Redmine does it.
-
Greg Hurrell
See also feature request #439, specifically this comment:
The system would need to be extremely customer-friendly, so that means that something as simple as sending an email to the support address should auto-open a ticket for them. The customer should be able to receive support via email, or via the web, and either way the entire history of the incident should be visible via the web interface.
Spam means that no auto-generated email could be sent until I had confirmed that the original message sent was not spam. In a way, accepting queries via email is better than doing it via the web, because it requires someone to actually send a message (unlike a web form where someone could enter any address even if they don't control it).
-
Greg Hurrell
I've been watching the support account for a few days now to see how much spam it's getting. About 100 messages so far; perhaps 20 or 30 per day.
So before we go live with this, I think I need some nicer method for mass-deleting spam tickets. This is likely to produce a lot of them...
Add a comment
Comments are now closed for this issue.