email interface into a module?

[Clement Chan]

The project that I am working on uses a fetchmail daeman to fetch the
bugs from the email server, and then calls procmail to run email_in.pl.
It is pretty neat and can be done. However it is run inside the
firewall, so security wasn't a major issue. The email password can be
exposed on the internet though. Procmail supports conditional parsing
every time when it is called. 

- Clement

On Wed, 2007-11-28 at 16:39 -0800, Craig wrote:
> I am using Bugzilla 3.0.1 (yes, I am upgrading to 3.0.2 this week. ;> )
> 
> We would like to enable the "email interface". However, our mail service
> is outsourced. I have written a simple script to talk to mail server
> (via IMAP) and grab the messages.
> 
> Obviously, I can then use "email_in.pl" via a system call. But, that
> seems kinda klunky... (But, it is a good short-term solution.)
> 
> I don't want to re-write the parsing routines or the logic checks. (And
> thus use the XML service on the bugzilla server.) I want to be able to
> *get* the emails in a custom way, do my own logic checks, and then have
> something else to parse the body and load it into the DB.
> 
> So, what if the bulk of the "email_in.pl" code was moved into a module
> (Bugzilla::EmailIn???)?
> 
> And then email_in.pl was changed to be just a "wrapper" that would read
> from STDIN, etc. But, the bulk of the work would be in the module (and
> thus available as an API).
> 
> I am a pretty decent perl programmer would be more than willing to code
> this up... but, wanted to ask if this sounds like a reasonable course.
> 
> TIA!
> Craig
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=cchan@mvista.com>