A simple regex that seems to always work for me for pulling the 'real' address out is this:
$from = $1 if $from =~ /<(\S+)>/;
If $from was "Usern name" test@test.dk, you'd wind up with 'test@test.dk'. If $from was just 'test@test.dk', it still would be since the regex wouldn't match.
As far as the problems of folding and multiple addresses in a field that jlongino pointed out, I think MIME::Head does a good job of taking care of the messiness of that for you. I have a script that used to do a lot of that manually, but I was always tweaking it for special cases that I'd never thought of. For example, addresses like "Name, User" <user@whatever> threw off my parsing of multiples because of the commas. And I started out thinking I only had to handle folding (wrapping onto multiple lines) for Subjects, but have now seen it in every header you mentioned, even the From header (The person had a very long user name in quotes). The perldoc is very long, but take a look at the 'get' and the 'unfold' methods to handle the problems of getting multiples and folding.
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|