That was a good point, so I attempted to do what you suggested. Strangely enough... it didn't give the error when I called my own version of that function.

This left the Bcc problem I was having as unresolved, and when I added Bcc recipients via the header command, I got emails to all listed, but the list of recipients was visible to everyone. So, looking back through the Net::SMTP documentation, I saw that email::send::gmail does not a make call like: 

$stmp->bcc(@recips,{SkipBad=>1});

[download]
and instead stuffs everything into the "to" recipients.

Long story short(er), I rewrote the send routine to properly parse out the bccs, remove them from the header, etc, and everything seems to be working, now.

Thanks for the help.

In reply to Re^4: Multiple Recipients in email by nephorm
in thread Multiple Recipients in email by nephorm

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.