mjustin

Habarisoft released new versions of the native STOMP client libraries for Delphi / Object Pascal for integration with popular open source message brokers: Habari STOMP Client for ActiveMQ 8.7 – tested with Apache ActiveMQ 5.18.4 and 6.1.1 Habari STOMP Client for Artemis 8.7 – tested with Apache ActiveMQ Artemis 2.33.0 Habari STOMP Client for OpenMQ 8.7 – tested with Eclipse OpenMQ 6.4.0 Habari STOMP Client for RabbitMQ 8.7 – tested with RabbitMQ 3.13.0 Release notes: https://www.habarisoft.com/release_notes.html

ScroogeXHTML for Object Pascal converts RTF (Rich Text Format) documents to HTML5 and other markup formats. This release adds BMP picture data extraction, a new option to handle invalid RTF headers, and many minor code and documentation improvements. Features Exports to stand-alone documents or embeddable fragments. Minimizes documents using CSS and default font definitions. Supports hyperlink fields, bookmarks, multi-language, and LTR/RTL text. Includes complimentary code for converting and embedding images as Data URIs. Conversion of pictures to a web-ready format may require third-party libraries. Includes an API for post-processing of the intermediate DOM-like document. Supports logging via the open source slf4p logging facade. Compatible with Delphi 2009 and newer and Free Pascal 3.2.2. Includes full source code. Resources Home page: https://www.scroogexhtml.com/object_pascal.html Demo version: https://www.habarisoft.com/scroogexhtml/8.7/ScroogeXHTMLDemo.zip User guide: https://www.habarisoft.com/scroogexhtml/8.7/docs/ScroogeXHTMLGettingStarted.pdf Release notes: https://www.habarisoft.com/scroogexhtml/8.7/docs/api/version.html Other platforms ScroogeXHTML is also available for the Java platform. (different feature set)

ScroogeXHTML for Object Pascal converts RTF (Rich Text Format) documents to HTML5 and other markup formats. This release fixes minor code issues and includes more unit tests and API documentation. Features * Exports to stand-alone documents or fragments for embedding in existing documents. * Minimizes documents using CSS and default font definitions. * Supports hyperlink fields, bookmarks, multi-language and LTR/RTL text. * Includes complimentary code for converting and embedding images as Data URIs. Conversion of pictures to a web-ready format may require third-party libraries. * Includes an API for post-processing of the intermediate DOM-like document. * Supports logging via the open source slf4p logging facade. * Compatible with Delphi 2009 and newer and Free Pascal 3.2.2. * Includes full source code. Resources * Home page: https://www.scroogexhtml.com/object_pascal.html * Demo version: https://www.habarisoft.com/scroogexhtml/8.5/ScroogeXHTMLDemo.zip * User guide: https://www.habarisoft.com/scroogexhtml/8.5/docs/ScroogeXHTMLGettingStarted.pdf * Release notes: https://www.habarisoft.com/scroogexhtml/8.5/docs/api/version.html Other platforms ScroogeXHTML is also available for the Java platform. (different feature set)

Meanwhile I managed to send email using MS Graph API. The example project with full source code is described here: Microsoft identity platform and OAuth 2.0 authorization code flow example for Daraja HTTP Framework The Authorization Code Flow with Proof Key for Code Exchange (PKCE) is a recommended OAuth 2.0 flow for native apps. No client secret is required in this flow. Instead, a secret is created by the calling application that can be verified by the authorization server. The example application requests an authorization code, redeems the code for an access token, and then calls the Microsoft Graph API to retrieve user profile data, and to send an email on behalf of the signed-in user. It may be a starting point for a ICS based application.

Update / new blog post: Microsoft identity platform and OAuth 2.0 authorization code flow example for Daraja HTTP Framework The Authorization Code Flow with Proof Key for Code Exchange (PKCE) is a recommended OAuth 2.0 flow for native apps. No client secret is required in this flow. Instead, a secret is created by the calling application that can be verified by the authorization server. The example application requests an authorization code, redeems the code for an access token, and then calls the Microsoft Graph API to retrieve user profile data, and to send an email on behalf of the signed-in user. Software requirements * Daraja HTTP Framework (https://github.com/michaelJustin/daraja-framework). The example code is located in the entra_auth_code_flow folder of the master branch. * Indy (https://github.com/IndySockets) with OpenSSL DLLs for Indy (https://github.com/IndySockets/OpenSSL-Binaries) * JsonDataObjects (https://github.com/ahausladen/JsonDataObjects) Daraja HTTP Framework download: - https://github.com/michaelJustin/daraja-framework

Send mails via the Graph API: a new example project for the Daraja HTTP Framework demonstrates how to get an access token using the implicit grant flow, and how to invoke the Graph API to send an email. No additional configuration is required, as the project uses an existing Microsoft Entra App registration , which is limited to the permissions for reading the user profile and sending emails. You may configure your own App registration and use its Application (client) ID in the source code of unit MainUnit, or contact me to provide a modified App registration.

Using ChatGPT I got some helpful basic steps: Q: How can a Delphi application use the Outlook.Application ActiveX to read a user calendar? A: To use the Outlook.Application ActiveX in a Delphi application to read a user's calendar, you can follow these general steps. Please note that you need to have Outlook installed on the machine where your Delphi application is running. (Steps and source code omitted) Q: Is it also possible to read the calendar of a different user? A: Accessing the calendar of a different user using the Outlook.Application ActiveX in Delphi depends on the permissions and configuration of the Outlook profile. Generally, the ability to access another user's calendar requires the appropriate permissions and security settings. (Again, steps and code omitted here, except the following two lines: // Replace 'otheruser@example.com' with the email address of the user whose calendar you want to access OtherUserCalendar := Namespace.GetSharedDefaultFolder('otheruser@example.com', olFolderCalendar); I do not post more as I am not sure if AI-generated answers are acceptable in this forum ---- Note: using the MS Graph API (or EWS) may be also an option, with the advantage that no local Outlook is required.

Habarisoft released new versions of the native STOMP client libraries for Delphi / Object Pascal for integration with popular open source message brokers: Habari STOMP Client for ActiveMQ 8.5 – tested with Apache ActiveMQ 5.18.3 and 6.0.0 Habari STOMP Client for Artemis 8.5 – tested with Apache ActiveMQ Artemis 2.31.2 Habari STOMP Client for OpenMQ 8.5 – tested with Eclipse OpenMQ 6.4.0 Habari STOMP Client for RabbitMQ 8.5 – tested with RabbitMQ 3.12.10 and 3.13.0-rc.2 Release notes: https://www.habarisoft.com/release_notes.html

Could you attach/upload the last version of your code? This would make it easier to reproduce the issue and to create a bug report for it.

The Content-Type header value looks suspicious: application%2Fjson RESTListResGroupResponse.JSONValue maybe is empty because the content type is not the expected one, application/json As can be seen in the screen shot, all other slashes are not encoded as #2F. If the request header Content-Type is not required, just remove it from the request setup and try if this helps.

Sorry for my mistake, I mistook a post of a different user as being from you. If the postman call succeeds, I'd check every single HTTP element and modify the Delphi request to be the same. Postman shows all headers and payloads. One header, which is frequently said to be causing errors, is the User-Agent. So I'd check and use the same header that Postman uses.

Did you check https://learn.microsoft.com/en-us/graph/api/user-get?view=graph-rest-1.0&tabs=http#permissions? A potential reasons for the 401 is the missing scope User.ReadAll. You wrote that you use Application type. For the Application permission type, the table says that the "Least privileged permission" is User.Read.All, however, yor code uses User.Read: RESTTokenRequest.Params.AddItem('scope', 'openid profile offline_access Mail.Read Mail.Send User.Read', TRestRequestParameterKind.pkREQUESTBODY); Also, for testing user profile access, there is no need to include the scopes profile, offline_access, Mail.Read and Mail.Send. Try this: RESTTokenRequest.Params.AddItem('scope', 'openid User.ReadAll', TRestRequestParameterKind.pkREQUESTBODY); The API documentation also explains that with Application permission type, only the admin can consent. Calling the API endpoint https://graph.microsoft.com/v1.0/me may return the admin user profile only. If you need the user profile of other users, use the HTTP request described in https://learn.microsoft.com/en-us/graph/api/user-get?view=graph-rest-1.0&tabs=http#http-request /users/{id | userPrincipalName} Hope this helps

Habarisoft released new versions of the native STOMP client libraries for Delphi / Object Pascal for integration with popular open source message brokers: Habari STOMP Client for ActiveMQ 8.4 – tested with Apache ActiveMQ 5.18.3 Habari STOMP Client for Artemis 8.4 – tested with Apache ActiveMQ Artemis 2.31.0 Habari STOMP Client for OpenMQ 8.4 – tested with Eclipse OpenMQ 6.4.0 Habari STOMP Client for RabbitMQ 8.4 – tested with RabbitMQ 3.12.7 and 3.13.0-rc.1 Release notes: https://www.habarisoft.com/release_notes.html

Does the server run out of resources? What does netstat say about client connections? Does the server cleanup (remove) stale connections?

With Indy, the recommended way to send a message to a specific client is to assign an unique client id to new connections in the OnConnect method of the server. The server application then can use the client id to limit the message to one (or some) of the connected clients. Technically, the client id would be a property in a subclass of the TIdContext class, and this class must be "registered" with the Indy TCP server. There are plenty of articles on the web covering this technique.