You might try putting in some debug prints to a log file you could check later (the contents of the %Env hash might be particularly useful if you suspect it's a security problem.

And while you say you're not trying to be too pretty yet, it strikes me as significantly easier to use one of the several mail modules (which would make it easier to debug, as well!) instead of doing raw socket writes. You might also investigate Archive::Zip (and Compress::Zlib) to do your zipping for you, too.

There's something to be said for building the walls and the roof out of pre-cut lumber rather than trees you uproot yourself.

In reply to Re: Windows Scheduler Issues by myocom
in thread Windows Scheduler Issues by seigniory

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.