in reply to Re^3: Problems sending an email attachment using Net::SMTP
in thread Problems sending an email attachment using Net::SMTP

Anyone who has worked at a large corporation long enough learns to choose their battles and this program isn't the right one and even if it was it isn't the right time. That's why I posted what my requirements/constraints are. For new monks I can see passing on the CPAN info, but for experienced members maybe, just maybe, you should give them the benefit of the doubt?

Elda Taluta; Sarks Sark; Ark Arks
  • Comment on Re^4: Problems sending an email attachment using Net::SMTP

Replies are listed 'Best First'.
Re^5: Problems sending an email attachment using Net::SMTP
by ww (Archbishop) on Jun 27, 2009 at 22:42 UTC
    I'm not questioning your experience, nor module-fu, but you won't be the only reader of this thread, today, tomorrow or....

    And when Monks have given my knowledge 'the benefit of the doubt,' I've had the regretable experience of continuing to stumble over blind spots.

    So, though this may not be an option for your, an observation for future readers: the referenced thread points out that, among other things, in many restrictive environments, it's possible -- as a workaround -- to copy paste the source of a pure-Perl module into your own script. Mail::Sender is such a module.

[reply]
      There's a certain etiquette to posts like that. Lead in with something like the following: "I know this likely doesn't apply to you, but for others reading this thread you may also find these CPAN modules useful, etc." Doing so indicates you have read the OP and that you understand the OP's situation.

      I also do not think it is appropriate to suggest copying some code as the copyright issues and company policies likely both still apply. Who are you to know more about their situation than they do? I understand the desire to help out, but gray area advice can result in more harm than help.

      Elda Taluta; Sarks Sark; Ark Arks
[reply]

        "...copyright issues...?"

        ...on a standard Perl module? Oy!

        "(C)ompany policies" may be an actual issue, but in that case an explicit, initial statement of the relevant restrictions rather than the newbie-ish "(a)nd I need to use core modules" might be a wise course.

        Tangentially, I resisted the inclination to note that I considered your two last posts "verged on the intemperate," but now I won't resist the temptation to suggest:

        • you not hide behind a "their" which means you
          ...or
          re-read my last previous. (Some of the very people whom you say might benefit may someday read this thread because they've encountered a similar issue. That's one of reasons the Monastery is an outstanding resource.)
          and
        • you avoid embarking on an OT lesson in egg-sucking, on the strength of a self-aggrandizing (if only implicit) and invidious assertion of being an "experienced member."
[reply]
        I also do not think it is appropriate to suggest copying some code as the copyright issues and company policies likely both still apply. Who are you to know more about their situation than they do? I understand the desire to help out, but gray area advice can result in more harm than help.

        If any of that applies, how can OP ask for code from perlmonks or anyone?

[reply]

In Section Seekers of Perl Wisdom