Is it possible to connect to an Exchange server using the MailCore2 framework? The documentation does not discuss Exchange Server support.
I want to build my own email client which can connect to the Exchange Server and replace Outlook. Can I use the MailCore2 framework?
If your Exchange server has enabled IMAP support, you can connect to the Exchange server using IMAP with MailCore2. This does not require any licence from Microsoft.
Related
I know of Domino C API EMs that add signatures via server not client to outbound SMTP emails, so this must be possible.
EM_MAILSENDNOTE can only be used on a client.
Here is another post that is relevant, but I'm not allow to add any content to it !!!
NSFItemAppend doesn't add text
I am looking for guide who have experience with Interactive Brokers Client Portal API. The Interactive Brokers CLient Portal API provides a gateway service.
I have tested this IB Gateway in my local and locally it is working fine.
The gateway is running on https://localhost:5000
I want to put this service on the windows server and want to access by server ip.
for example: https://52.xx.xx.12:5000 like this
I also tried solution from this reference Running interactive brokers client portal API in cloud server but not got success
Thanks
You need to set your server IP address in IB gateway setting as a trusted IP, and you should open 5000 port in firewall as well.
Our application has government requirement for all HTTP requests to include SSL client certificate and all application servers to check incoming requests for client certificates.
Does ejabberd community edition support c2s certificate auth?
https://www.process-one.net/en/ejabberd/protocols/ says that XEP-0178 on community edition is only implemented for S2S communications, but on https://process-one.net/logs/ejabberd#conference.process-one.net/2018/07/09.html someone called says,
"'c2s_' is for client auth, as opposed to 's2s_'. Maybe you've seen old docs that said it's a Business-only feature, this went into the Community Edition at some point."
So, is it in community edition as well?
I'm pretty confused concerning the terminology used by IBM. I'm currently working with Watson IoT and embedded devices using MQTT. As you know, embedded devices sometimes do not have the capability to secure a connection via certificates (former SSL). Watson IoT therefore offers a secure connection (?) called "TLS with authentication token". That's what's confusing me. I learned that for a SSL (now TLS) connection you need to pass certificates to the server. How can you establish a TLS connection just by using/sending a auth token? Or do they just mean the authentication process instead of a secured and encrypted connection?
Thanks in advance and have a nice weekend!
If you're using MQTT, the simplest way to connect your device to the Watson IoT Platform is as follows:
When you register your device, you define (or get given) an authentication token - in effect, a password for that device. You have two main options on how you use this token to connect the device to Watson IoT Platform at orgId.messaging.internetofthings.ibmcloud.com:
Port 1883 (this is non-TLS)
Port 8883/443 (this is TLS)
In both cases the password is used to authenticate your device - but only in the second is the on-the-wire traffic encrypted (which is why we strongly recommend using TLS/port 8883/443 where possible). The encrypted connection is over TLS: Watson IoT Platform presents a certificate to allow your TLS-enabled device to validate the certificate and hence trust it's talking to Watson IoT Platform.
There are further options to build on this. You can configure device certificates (e.g., see here) - but I haven't discussed these as - hopefully! - I'll have answered your question using the simple patterns above. Further details on connecting to the platform are available here.
Links correct at the time of writing
If I get the connection details from a service provider who needs the ESME to talk to SMSC in SMPP, do I need to have my own SSMP server running on my machine too? Or can I just build a client to connect to SMSC And send SMS? I am using JSMPP to send sms.
To send SMS through a provider, all you need an ESME which will connect to the SMSC of the provider. This is independent of SMPP library you are using.
If you want to test your ESME and the SMS(s) the ESME is sending, you would be better of with your own SMSC.