It's a home grown thing. It was created by an in house sys-admin about 5 or 6 years ago, but that guy has dropped off the face of the planet.
I just mentioned Jira because I figured everyone would know what that is and that's the closest thing I could think of to what they've got. They want to add this functionality to their existing stack specifically because a Jira salesman stopped by and wow'd them with it :D Since it's the only real "we want it, but don't have it" feature that's driving them to Jira, I'm just bidding on the effort involved. If my bid is lower than the cost to license Jira and train everyone on how to use it, then of course I'll be the implementor on it. It's a perl stack with a postgres backend, I have no idea what the email system is though. I do think scripting access to a POP3 email box might be the most direct solution. Then just have it run a cron job every few minutes, unless there is a way to make a daemon that can get a push notification. By the way, is there any compelling reason for POP3 vs IMAP vs whatever for this use case? I realize that POP3 downloads all the messages at which time they're deleted off the server. I think they use either IMAP or exchange in house because they have a webmail system that I saw most of the people using. However I can confirm that they don't use outlook webmail, nor is it a hosted type of gmail for business as far as I can tell. (if it is they have skinned it beyond all recognition). I'm guessing most mail systems support both POP3 and IMAP these days. (I should probably ask them though, that's the type of assumption that ends up costing me on these types of bids) :) On Wed, Jun 4, 2014 at 9:47 AM, Lonnie Olson <[email protected]> wrote: > On Wed, Jun 4, 2014 at 7:26 AM, S. Dale Morrey <[email protected]> > wrote: > > They want to track certain conversations automatically and log them to a > > JIRA type system. > > Are you just talking in general, or specifically JIRA. JIRA and most > other bug/ticket systems already have the code necessary to respond to > emails. > > https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email > > For the custom option, I have another handy trick for Corey's strategy #2. > If you don't want to process the email on the mail server, you can > also forward the email from the mail server to the bug tracking > server. > > Something like this in the mail server's aliases: > bugs: bugs@bugserver > > Then just make sure the bugserver can receive email, then pipe it to > your script. > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
