. I've completely fogot about this approach.
Just to expand the idea a little bit, you (the OP) could create an e-mail address specific for this task (assuming the mail server resides on the same machine as the Perl log
script*). For an example system_log@your_domain.com.
Then you can, as Xenograg
wisely suggested, make a script that checks this e-mail account and do the append stuff. This approach has at least two advantages from my original post:
- You don't have to make a "valid e-mail addresses" list, since this account will only receive e-mails from inside the company and therefore won't be "exposed" (if I've understood correctly).
- You can even treat information that was or not logged by looking if the e-mail message was already read or not.
* I've stated this for the sake of performance and to the application to be practical. If the mail server is in another machine I think this could get a little messy.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.