DECODING MAIL FROM WEB SERVER IN PLAIN TEXT FORMAT(THE MAIL BEING SENT BY LABVIEW APPLICATION)

[smercurio_fc]

I'm not sure how that invalidates what I said, which is that the client app is not decoding the attachment properly. You yourself said "A decent mail client will recognize the encoding and convert it back to whatever is necessary before presenting it to the user.". Shouldn't the application that's being used be able to do the same thing if it's programmed properly? After all, the application may not know how the email was sent. True, in this case there's a certain level of control since the email is being sent via LabVIEW, but that can change.

As I noted in my response, I wasn't able to use the LabVIEW SMTP VIs since those don't work with authenticated servers. I used the OpenG SMTP library.

[rolfk]

---

@smercurio_fc wrote:
I'm not sure how that invalidates what I said, which is that the client app is not decoding the attachment properly. You yourself said "A decent mail client will recognize the encoding and convert it back to whatever is necessary before presenting it to the user.". Shouldn't the application that's being used be able to do the same thing if it's programmed properly? After all, the application may not know how the email was sent. True, in this case there's a certain level of control since the email is being sent via LabVIEW, but that can change.

As I noted in my response, I wasn't able to use the LabVIEW SMTP VIs since those don't work with authenticated servers. I used the OpenG SMTP library.

---

I'm sorry if I misunderstood you. I saw that you said something about that this all is strange and it is not as far as I'm understanding the issue so far. It is simply logical, and the problem is because the LabVIEW SMTP VIs are in fact to smart for what the end application expects.

I'm pretty sure that that application the OP is using does not do any decoding at all. It probably just takes whatever is sent interpreting it as ASCII-7bit character (or considiring the remark about the pipe symbol even as ASCII-8bit which would be sort of even wronger) only and goes to chew on it.

The type of actual encoding is always mentioned in the mail header or the according section header, but of course has to be read and accordingly processed. And it can be a real challenge to do correct on the client side since there are so many possible encodings. That's why I mentioned processing the mail by a real mail client before feeding it to the application in question.

Rolf Kalbermatter

[smercurio_fc]

No apology necessary. I didn't think you were castigating me, or something.

What I had actually found strange was the comment by the original OP who had said ""When we open the attachment its perfectly alright.But when it is decoded by another application its getting some extra characters" without really giving a proper explanation, though this was later done.

I agree with you that short of making this other application "decode-aware", the stop-gap solution would be to use an email client to properly decode the attachment.

Alternatetively, the OP can use the OpenG SMTP libraries and try to modify the code in order to "encode" (generally speaking) the attachment so that the other application will handle it properly.

[user_1]

Hi Rolfk,

Thanks for the reply.

So what can i do for this from my part of labview coding?

The labview application is used for the purpose of sending mail only.

Other works are not handled by labview.

In this send mail part can i do anything to cure the problem?

I am herewith attaching a screen shot of the send mail portion of my blockdiagram

Thanks again........

[rolfk]

---

@user_1 wrote:

Hi Rolfk,

Thanks for the reply.

So what can i do for this from my part of labview coding?

The labview application is used for the purpose of sending mail only.

Other works are not handled by labview.

In this send mail part can i do anything to cure the problem?

I am herewith attaching a screen shot of the send mail portion of my blockdiagram

Thanks again........

---

As smercurio so kindly recommeneded already TWO times, use the OpenG variant to send your text. These VIs are much simpler and do not do character encoding as far as I know, which for most mail clients would be the WRONG thing to do, but since you asked.

Rolf Kalbermatter

[smercurio_fc]

You can get a corrected version of the OpenG SMTP library here.

[user_1]

Hi,

Thank you somuch.

My labview version is 8.0.1

[smercurio_fc]

There's a version for 8.0 in reply #6.