I'm not an expert when it comes to Perl by any means, but I'd personally let the mail go into a mailbox and parse it from there, rather than grab it from STDIN.

Let the mail delivery system worry about getting the messages into the right place, and more importantly, written to the filesystem - so that you've got a chance of recovering some information if something goes wrong (i.e. power outage, OS crash).

Once you're sure that you successfully inserted the information into your database, then you can delete the message from the mail spool.

As far as I can make out, your current setup is

In my head you could let the mailsystem handle the first 2 steps - I'd start by slurping the mailspool into a parser.
Baz.

In reply to Re: Handling Incoming Mail by BazB
in thread Handling Incoming Mail by Ian the Terrible

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.