Wc -Sx- Jones wrote:
=pod What would the best approach to account for ALL strings matched? (In other words I want to display as complete a list as possible to determine all strings that would be matched...) =cut
$ podchecker ~/Wc-Sx-Jones.email
:) I was wondering why no one did that check before.
s/((?:bounce[ds]?|no(?:list|reply|response)|return|sentto|\d+).*?)(?:[\+_\.\*-]\d+\b)+/$1-ID/oi;
The characters '+', '.' and '*' are not special in a character class and don't have to be escaped. The /o modifier is only useful if you have variables in the regular expression.
Could you please explain in a little more detail what you are trying to accomplish.
It matches and shortens e-mail (addresses) replies from lists:
[EMAIL PROTECTED]
And spits out
[EMAIL PROTECTED]
Which is all fine, this way my report isnt horribly mangled by 500 lines just from one listserv; but I was wondering about reverse engineering - what all does it actually match.
Just thinking out loud... -Bill- __Sx__________________________________________ http://youve-reached-the.endoftheinternet.org/
PS - You can get the program in question at: http://jimsun.linxnet.com/postfix_contrib.html
And you can run it like:
perl /usr/local/bin/pflogsumm --verp_mung=2 -d yesterday \ -i --zero_fill --problems_first --mailq --verbose_msg_detail \ /var/log/syslog 2>&1 |/usr/bin/mailx -s "`uname -n` Daily \ Postfix stats" postmaster
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
