Jon Erickson

We know. Just looked at the composer.lock and one small package requires PHP 8.1. Will add a PHP 7.4 composer package requirement and update the dependencies to make sure it doesn’t happen again. 

Yes, it has always been designed to run on CIC. However, I can’t test against CIC as I do not have a CIC service to use to test. We only use an on premise license to test against. 

A new version has been submitted with support for 4.7.2 and PHP 8.1. The AWS SDK was also updated which added support for PHP 8. Previously did not support PHP 8.

A new version has been submitted with support for 4.7.2 and PHP 8.1. The AWS SDK was also updated which added support for PHP 8. Previously did not support PHP 8.

Update has been submitted and approved.

Update has been submitted and approved.

I am not aware of this issue. Can you elaborate or send me a PM? Thanks. 
@Stuart Silvester just saw your email. Thanks. 

I am not aware of this issue. Can you elaborate or send me a PM? Thanks. 
@Stuart Silvester just saw your email. Thanks. 

Thanks for bringing this up. Will get this addressed. 

Every time SES recognizes a bounce, it will send a notification to your community utilizing the API. You can then choose what is done when one is encountered. There is a list of different options include setting their status so they no longer receive emails. 

Great suggestion.
As for the error, you need to have the IMAP PHP extension enabled.
https://phpadvices.com/install-or-enable-imap-extension-in-php/

Great suggestion.
As for the error, you need to have the IMAP PHP extension enabled.
https://phpadvices.com/install-or-enable-imap-extension-in-php/

@Jon Erickson: Your window of oppatunity has opened even more with this.
From time to time, I still get asked about the webview apps and notifications. It's worth throwing your crown into the area as a solution I think. 👍

You can also try out the following app to get rid of SMTP and use the AWS SES API for better performance and less impact on your server.
 

Most likely a spam bot without an account, posting a message, and then being sent the “continue registering…” email to the fake email address. Happens a lot!
Also the application will properly handle the bounce if the email is not an actual member account!

Yes, I think the issue is that I prune my settings every 7 days which applies to all logs, so if an email bounced last month, I have no way of searching it quickly via logs or a search. Thanks!

Have you set them up using AWS’ SNS service? Directions are found in the app description. Every time AWS sends a notification to your IPB community, a log will be entered!
As for the prune settings and search functionality, no problem!

Unfortunately we have no way of knowing unless one of our clients who utilizes both apps can report their success.
However, we have built our app in a way that doesn’t “reinvent the wheel” but uses IPBs core email sending functionally. So unless some app took drastic measures to send email a different way, I’d imagine they play well together. 
Great idea. That would definitely be an issue!

A quick idea : admins and moderators should be exempted from automatic bounces actions : if for some reason the mail server was to bounce for admins, admin accounts may be flagged as spammer or disabled which could end up in the ACP being unaccessible to anyone...
This would be very bad :).

For help and support with the AWS Simple Email Service Application. Ticket and Forum support can also be obtained at https://www.deschutesdesigngroup.com/support.
Installation Instructions: Instructions can be found on the marketplace page. Click the link below.
 

For help and support with the AWS Simple Email Service Application. Ticket and Forum support can also be obtained at https://www.deschutesdesigngroup.com/support.
Installation Instructions: Instructions can be found on the marketplace page. Click the link below.
 

my request:
can we get documentation for adding API to our apps, I'm having to add it to 3 different apps atm for a project for a client, and i'm really sorta winging it. looking at what you guys have done, but even then its not all that clear what is being done or why. please document the graphql api you've added, i'm assuming you are using this in your mobile app, since i can't find any reference to it in any of your php/js code. '/^\s*\*\s*@([a-z]*)(\t+([^\t]*))?(\t+([^\t]*))?(\t+([^\t]*))?$/', found in /system/Api/Controller.php line 319. hopefully I can express how much misery this regex has caused me. you guys are literally the only software or framework i know of, in php or not, that uses tabs in their code. I use spaces, the rest of the world uses spaces, I have git hooks that will actually reject code for using tabs instead of spaces, my IDE is configured to use spaces. so for like .00001% of the over all app, on stuff that isn't even code, i have to undo ALL of that, just so the api reference docs are processed and shown in the ACP for the other devs on this project to have easy access to that info. I spent a good long while trying to figure out why it was not showing or throwing an exception in the api references, as there was no clear indication as to what was causing it or why. so for sanity sake, please make this regex more robust to look for tabs or space (or better yet, not rely on phpdoc block for api reference, make it a json/xml/txt in <app>/data that can be read and parsed out).  $this->_respond( json_encode( $output, JSON_PRETTY_PRINT ), $response->httpCode, NULL, $shouldLog, TRUE ); /system/Dispatcher/Api.php line 338/342/348., this code does not always produce valid json. it looks like json, but its not, its corrupted. I've had to add 'JSON_HEX_QUOT | JSON_HEX_TAG ' to the flags section of json_encode to get it to produce valid json (i did this thru a hook, but had to overload the entire method, cause there was no point in the code execution, i would be able to add those 2 flags). So please either add those flags or move the json_encode to a method inside the dispatcher, where all it does is json_encode, that way i can hook it and add those flags or any other flags i might need in the near future.  editor content from the api doesn't not get the file or url place holders replaced, i was pulling articles and blogs records, and none of the internal links or attachments were showing up, cause they still had the and <filestore> stuff still in them, so i had to go hook blogs and articles api to parse them (haven't gotten to the other apps yet).  embed/iframe content also is not loaded, cause the src attribute is empty, as the source is still on data-embed-src (i'm assuming this is apart of the IPS lazy loading that didn't get scrubbed properly). on db records, you include a title property but in 'fields' property, it also includes the title field content as well, so if that can be removed or at least give us the ID of which field_# is the title, same for description.  can you also include for any dates, a rfc2822 format along with the rfc3339, as javascript does not like the rfc3339 one (example: DateTime::ts($sometimestamp)->format(RFC::882), this will return a rfc2822 formatted date). heck even a raw unix timestamp would be better than a rfc3339 :).  to be completely honest, the api has not been a pleasure to write code for or to work with. it is one of the most difficult API's i've used. I have spent about 20 times longer debugging and finding solutions, than i have actually writing code to use the api. any way, i hope you guys can address these issues, if not, I might be forced to abandon the api and find another solution.

Fantastic. Thanks! Conclusion is - I am blind.

You can also email support@invisionpower.com 🙂 

Thanks for the support however I can't commit to any specifics as I have no control over the app review process and there are many unknowns in the whole development process. Promising features in a specific timeframe is the quickest way to poorly developed applications 😉