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

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.

  • Comment on Re^5: Problems sending an email attachment using Net::SMTP

Replies are listed 'Best First'.
Re^6: Problems sending an email attachment using Net::SMTP
by Argel (Prior) on Jun 29, 2009 at 20:57 UTC
    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]
        You shifted to a more generic case about letting others know even if not applicable to the OP. My remarks are in the context of that shift. If someone wants to post information for others then that's fine, but they should indicate that that is what they are doing. That's the courteous thing to do for OP, who will not be able to use the information being provided. It's a way of saying "yes, I read your post and understand your situation". Without that it looks like you either didn't read the post or are talking down to the OP. Does that make sense?

        Regarding hiding behind words. I was speaking about the more general case you brought up. That in this case I am part of that general case goes without saying. In essence I was trying to say that everyone should try and take the OP's feelings into consideration, whoever that OP is.

        "Experienced" as in I have been on here long enough to know about Yes, even you can use CPAN. For new users maybe assuming they do not know about it is okay but for long time (i.e. experienced) users it makes more sense to take the opposite approach.

        Looking back I probably did not explain myself very well and for that I apologize.

        P.S. Mail::Sender is not a core module (or if it is it's not in the ActivePerl distribution I am using).

        P.S.S. Would that be a European or African Swallow egg? ^_^

        Elda Taluta; Sarks Sark; Ark Arks
[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]
        Not everyone asks for code. People can be looking for articles, etc. And e.g. in my case I was asking for help debugging my program, so the changes ig graciously made would be a derivative work. You also seem to be overlooking that the issue could be the license used by the perl modules in question. Anyway, there are many ways to ask for help and many ways to give help, not all of which will violate company policy (or personal ethics, etc.).

        Elda Taluta; Sarks Sark; Ark Arks
[reply]

In Section Seekers of Perl Wisdom