Exchange-Web-Services-for-PHP | basic library for interacting with Exchange Web | Email library

by rileydutton PHP Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | Exchange-Web-Services-for-PHP Summary

Exchange-Web-Services-for-PHP is a PHP library typically used in Messaging, Email applications. Exchange-Web-Services-for-PHP has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This is a basic library that abstracts a few of common operations using the Exchange Web Services API present on Exchange Server 2007. It is based in large part on [Talking SOAP with Exchange] Right now only basic operations are supported (getting a list of all email from a user’s inbox (including attachments), sending email messages, getting calendar events, and utilizing Delegate support to access multiple accounts), but as time goes on hopefully more funtionality will be added.

Support

Quality

Security

License

Reuse

Support

Exchange-Web-Services-for-PHP has a low active ecosystem.

It has 87 star(s) with 44 fork(s). There are 11 watchers for this library.

It had no major release in the last 6 months.

There are 25 open issues and 5 have been closed. On average issues are closed in 297 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Exchange-Web-Services-for-PHP is current.

Quality

Exchange-Web-Services-for-PHP has 0 bugs and 0 code smells.

Security

Exchange-Web-Services-for-PHP has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Exchange-Web-Services-for-PHP code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Exchange-Web-Services-for-PHP is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

Exchange-Web-Services-for-PHP releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Exchange-Web-Services-for-PHP saves you 248 person hours of effort in developing the same functionality from scratch.

It has 604 lines of code, 29 functions and 5 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed Exchange-Web-Services-for-PHP and discovered the below as its top functions. This is intended to give you an instant insight into Exchange-Web-Services-for-PHP implemented functionality, and help decide if they suit your requirements.

Do the actual request
Create curl buffer
Read from the current stream
Open a stream
Retrieves information about a file
Write data to the stream
Get the headers of the last request

Get all kandi verified functions for this library.

Exchange-Web-Services-for-PHP Key Features

No Key Features are available at this moment for Exchange-Web-Services-for-PHP.

Exchange-Web-Services-for-PHP Examples and Code Snippets

No Code Snippets are available at this moment for Exchange-Web-Services-for-PHP.

Community Discussions

Trending Discussions on Exchange-Web-Services-for-PHP

PHP exhausting memory size using SoapClient

QUESTION

PHP exhausting memory size using SoapClient

Asked 2018-Mar-09 at 16:16

Today my PHP application started to fail using it's email parser technology from https://github.com/rileydutton/Exchange-Web-Services-for-PHP which has worked for years.

Prior to this, the EC2 drive filled up and the site went down. I resolved the free space issue and the site came back except for the parser. I then updated the system as usual via yum and restarted services. I then rebooted the whole server.

The logs state that:

Uncaught SoapFault exception: [Client] Allowed memory size of 314572800 bytes exhausted (tried to allocate 1052319233 bytes) in /var/www/html/core/php/owaews/lib/NTLMSoapClient.php:10

That is the initial construct code connecting to the WSDL.

The requested memory amount changes, but this code hasn't changed in years so I'm surprised it is acting up.

PHP is set to allow 300MB of memory_usage.

I'm wondering how I can resolve this issue and its root cause.

Currently running Amazon Linux 2017.09 4.9.85-37 with Apache 2.4.27 and PHP 7.1.13 using FPM/FastCGI

...

ANSWER

Answered 2018-Mar-09 at 16:12

Okay, apparently loading the WSDL remotely was causing the memory issues. Initial thoughts are changes on the OWA side returning some odd data that the site was choking on.

Thankfully, the parser code allows you to load the WSDL locally, and the problem does not occur when loaded locally.

Source https://stackoverflow.com/questions/49195746

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Exchange-Web-Services-for-PHP

You can give this a shot, but it doesn’t work for me on my Exchange server. If it doesn’t work for you, don’t panic, just see the "Advanced Installation" section below.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: