Hi - I'm trying to send an e-mail in case of failed refreshing of .iok files in a chain action (I attach a doc file with configurations applied).
Making a test, I get the error reported in the attached file (client does not have permissions to send as this sender).
I contacted our technical support that verified that connections with our MS Exchange server are ok. Using this connection, they were also able to send emails with the same sender from our Omniscope server using standard protocol smtp commands.
I'd like to know if I have to set some particular configuration (perhaps in the wrapper.conf file) to send emails from within the Omniscope Scheduler.
We need to first identify if you can send an email successfully via Omniscope Desktop. Could you please try the following:
1. Open up DataManager in Omniscope Desktop 2. Add in a new 'Email output' from the 'Outputs' options and attach it to the Omniscope block. 3. Enter your mail server credentials and attempt to publish (i.e. send the email)
just a quick confirmation: are you suggesting to set up our Exchange server to support POP3/IMAP access? Do you think that this is going to work also on Omniscope 2.7 Server Edition?
At the moment the Omniscope email connector supports connecting to POP3 or IMAP email services. We do not support Exchange by default, however you should be able to setup IMAP access to your Exchange server. After you do this you should be able to connect using Omniscope.
today I received confirmation that on our Exchange Server POP3 and IMAP protocols are already open. Unfortunately, nothing changed. Is there some specific configuration we should do?
You need to contact your server administrator and ask them to provide you with the POP-3 and IMAP connection details (server URL, port and SSL). As an example, POP3 servers typically listen on port 110 and IMAP servers listen on port 143, but this may have been configured differently by your admin.
Today I got an answer from our server adimistrators that confirmed me that these are the POP3/IMAP details:
POP3 – port TCP 110 IMAP – port TCP 143
They confirm me that they made a test connecting the Omniscope Server to the Exchange Server using telnet on the two ports indicated (for IMAP and POP3 protocols). In both cases they were able to establish successful connections.
Unfortunately not! I was just waiting an answer from our administrator for server POP3 and IMAP configuration, but the situation is still the same. Sincerely, this is not an high priority open point at the moment (but we would like to solve it sooner or later).
So are you now able to connect to the exchange server using POP3/IMAP? What error do you get and when does it happen. I appreciate this might not be high priority but we would be keen to help you resolve this issue as we have a number of clients who want to connect directly to Microsoft Exchange from Omniscope. Would it help to arrange a short phone call/screen-sharing session?
the problem is still the same: trying to sent email I get the error reported in the file I attached opening this discussion (client does not have permissions to send as this sender).
You asked me about POP3 and IMAP connection details and I got the answer today from our administrator (that standard configuration is used).
I don't know if a phone call can be usefull. Do you have any idea about some test I can do or about any Omniscope configuration I can check?
I think it would be useful to arrange a short screen-share if that would be possible, that would allow us to run through a few different tests and configurations. If you think that would be useful please contact me directly at: support@visokio.com
Have your network admin's setup POP3/IMAP connectivity on your Exchange server? If so I'd be more than happy to arrange a screen-sharing session with you to see if we could get this working.