I guess I just need a point the right direction or a suggestion of a particular function or tutorial so I don’t spend hours trying to do something that isn’t possible to do in the first place.
A big ++ for that alone. I tend to do just that - seek advice only after everything else has failed. Being a complete autodidact, it's sort of tradition. But seeking advice beforehand has - apart from learning being much lighter - a big sociable effect.
My plan is to write a pre-processing script that will split up the main mail log file into several files based on the sender email address.

Why? Did you hit any boundaries with pflogsumm? Is splitting even necessary?

Splitting up a mail log file is tricky, since the sender (envelope) address isn't the reference for log entries, afaik. Each mail gets assigned a message ID, and depending on the mailer, a processing identifier which might change through the delivery chain, depending on setup. If you have e.g. a sandwich setup, postfix delivering to spamassassin and a virus checker, then picking up the message again with a second instance of postfix, the internal IDs will likely change; you would then have to take that into account. Having all that done and producing a set of output files suitable for pflogsumm, you will have either rewritten or duplicated a large part of pflogsumm itself.

Since you didn't mention any constraints of your setup yet (processing speed? memory? disk space?) but only spoke of your plan, more information is needed to give good advice. What has been the outcome of using pflogsumm "as-is" so far?

--shmem 

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

In reply to Re: Most efficient (or fast) way to split a postfix mail log file? by shmem
in thread Most efficient (or fast) way to split a postfix mail log file? by oltranzista

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.