11-05-2021 08:01 AM
Have you gotten with your Exchange Server Admin and had him inspect traffic coming in via your email attempt? Start there first.
This thread reads as if you have done zero research and are blaming LabVIEW for your problems without doing any investigative work.
11-05-2021 08:17 AM
Our Administrator tried to check the logs and found nothing unusul or suspicious.
I have to admit this is a bit frustrating!
I will try to use a system call to get the email out.
Thank's for your support
11-05-2021 10:26 AM - edited 11-05-2021 10:29 AM
There are a couple of things that you need to get with your Exchange Server Admin and verify.
Your Exchange Admin should be able to verify these for you.
11-05-2021 10:50 AM
@Lab_CD wrote:
Our Administrator tried to check the logs and found nothing unusul or suspicious.
One other note: You are not at this point yet. You should have asked him/her if the email that you attempted to send reached the server.
11-05-2021 06:14 PM
@Lab_CD wrote:
Hi Bill,
The test using an external server such as Office365 would indicate both servers are configured to be incompatible with LabView E-mail Client, right? Is there an alternative way of sending emails using Labview?
Thanks
"Office365 Server"? You didn't mention "server", so I assumed you meant you tried to reach this server with LV and with Office365, which I assumed was Outlook.
11-05-2021 07:30 PM
The VI diagram he showed was clearly using the SMTP Email VI functions. And Office365 is simply the collection of several Microsoft tools into a platform solution. That includes the Exchange server as email solution.
11-06-2021 10:05 AM - edited 11-06-2021 10:06 AM
@rolfk wrote:
The VI diagram he showed was clearly using the SMTP Email VI functions. And Office365 is simply the collection of several Microsoft tools into a platform solution. That includes the Exchange server as email solution.
Yes, but when someone mentions "Office365" in a standalone way like that, it isn't incorrect to assume that they mean the suite of tools traditionally deployed to a workstation, which does NOT include the Exchange server, but DOES include Outlook. (Why not just say, "Exchange Server"? That's much more concise.)
11-06-2021 10:28 AM
11-06-2021 05:46 PM
@rolfk wrote:
@billko wrote:
(Why not just say, "Exchange Server"? That's much more concise.)Have you looked at the title of this thread? 😀😁
Yes, but that, along with the mention of Office365 without linking that to Exchange Server still suggests trying two different clients - LV and Office365 - trying to reach the Exchange Server. Other posts here seem to have assumed the same thing.
11-08-2021 09:30 AM
Hi Eric1977,
Thanks for the answer. I don't want to blame anybody here - I just wanted to trace down the problem. Sorry for not beeing precise enough.
I did some tests before starting this thread, but haven't mentioned it in detail. Sorry again!
>Is the Outgoing Mail Server correct?
Yes (it is working with an alternative tool (SMTPDiagPro | (skittel.de)) on the same machine)
>Is the Port Correct? You have 587 as the port. Verify that.
Yes (it is working with an alternative tool)
>Do you need login credentials? Your screen capture says yes. Have you tried it without?
>If yes, are your user and password correct?
Yes (it is working with an alternative tool)
>If they are, are you sure that after so many tries that it disables them or are your credentials disabled for a different reason?
I cannot answer this, but using the other tool, works.
>Your using TLS\SSL. Is that a requirement? Have you tried it without?
Unfortunately yes. Sorry I cannot switch it off.
best regards