I would love to and perhaps even enjoy using any one of the CPAN modules provided they worked on the mail. I looked through them and tried the MailTools, and that (being what my previous thread that I referenced) failed and I don't know why.
Were I to know why, it would make life easier, but that module apparently doesn't have any error handling. It just dies quietly and peacefully, leaving me wondering what it doesn't like about the files.
If I had to guess, I would guess that Windows gets an "\r" in there and that breaks it - but I haven't had time today to go and test out that theory (removing any "\r" in there and then trying to grab the headers with Mail::Internet and/or its Mail::Header.
If you have a specific module in mind that you think would work, even if MailTools fails, I'm all ears.
I am just a little gun shy to go running and out and trying them all (I am on Windows and using ActiveState, which IMO is more annoying than using Perl in a *nix environment) and not having any of them work - leaving my exactly where I was, but having spent a lot of time learning which ones don't work and nothing else.
I did attempt to look over the RFCs for the email, but the depth of reading was hard for me to justify for a script that is in the end to track spam stats on our mail server.
I am hoping that someone that is already far more knowledgable about it would be willing to pipe up and save me the time, but if not, perhaps I will be doing this in my free time then, rather than on the clock at work since they have a stack of other things I need to get done first.
There are some odd things afoot now, in the Villa Straylight.
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.