in reply to Re: Sending a email with file attachment with LWP ONLY
in thread Sending a email with file attachment with LWP ONLY

You're giving people wrong ideas with your sloppy wording.

if you don't use MIME, you're not sending email

It is possible to compose Internet messages without MIME, in fact more than half of my outgoing emails are not MIME. Mind that the "E" in the acronym is for "extensions".

Sending email is a different concern.

even if you send through a web interface ( webmail )

It is clear from the problem description that the end user invokes his local desktop mail client through the mailto URI in that Web application.

it must uses MIME on your behalf -- otherwise it isn't email (can't use email addresses)

Email addresses are a different concern. The problem description was about attachments, and we should suppose the addresses in that mailto URI work just fine.

  • Comment on Re^2: Sending a email with file attachment with LWP ONLY

Replies are listed 'Best First'.
Re^3: Sending a email with file attachment with LWP ONLY
by Anonymous Monk on Jul 05, 2012 at 13:21 UTC

    It is clear from the problem description that the end user invokes his local desktop mail client through the mailto URI in that Web application.

    No. What does the local-desktop-mail-client have to do with LWP?

Re^3: Sending a email with file attachment with LWP ONLY
by Anonymous Monk on Jul 05, 2012 at 12:37 UTC

    You're giving people wrong ideas with your sloppy wording.

    On the other hand, you're giving sloppy-question-asker wrong ideas with your hypertechnical but ultimately irrelevant corrections

      Irrelevant? MIME stands for Multipurpose Internet Mail Extensions. "Extensions," therefore not part of the core system. The OP needs to send attachments, so it's true that he's going to have to use MIME, but the claim "if you don't use MIME, you're not sending email" is completely wrong, and deserved to be corrected. You most certainly can send email without MIME.

      Aaron B.
      Available for small or large Perl jobs; see my home node.

        Attachments were routinely sent prior to the advent of MIME. You'd just encode the file using UUEncode, paste the result into the body of the message and send it. It might sound somewhat manual, but in practice mail clients could automate some/all of that, albeit with some false positives and false negatives in detecting where attachments began and ended.

        perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'

        Irrelevant? ... The OP needs to send attachments, so it's true ...

        Exactly -- no need to scrutinize every syllable as if I'm writing an encyclopedia