Jon Erickson

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 😉

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 😉

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 😉

1. If mail is bounced put user to validation group till they update and put correct address.
2. If they complain for email (complain report) - deactivate the user ID. 
 

FYI we are building bounce and complaint management into our AWS SES app. Are there any specific features you’d like to apply to members when a bounce or complaint is returned from their email besides moving them groups, and sending them a message?

FYI we are building bounce and complaint management into our AWS SES app. Are there any specific features you’d like to apply to members when a bounce or complaint is returned from their email besides moving them groups, and sending them a message?

FYI we are building bounce and complaint management into our AWS SES app. Are there any specific features you’d like to apply to members when a bounce or complaint is returned from their email besides moving them groups, and sending them a message?

I finally upgraded to 4.5 and using he API got rid of the posting lag associated with SMTP. The app is great, highly recommended.

I think most of the posts in this topic have covered it. Utilizing the API over SMTP is significantly faster. If your community is sending many emails a day, this will help speed up your site. 

In most cases, a configuration set will not be needed. It allows you to add a set of defined rules from AWS to your emails that get specified in the email header. These are things that are invisible to the average user. For example, you can have AWS track metrics on your emails sent and then have the metrics published to another AWS service. This is advanced usage case but possible with configuration sets. 

In most cases, a configuration set will not be needed. It allows you to add a set of defined rules from AWS to your emails that get specified in the email header. These are things that are invisible to the average user. For example, you can have AWS track metrics on your emails sent and then have the metrics published to another AWS service. This is advanced usage case but possible with configuration sets. 

@Jon Erickson

Just purchased and set it up with no problems. Could you possible explain the advantages of using a configuration set?

I looked on Amazon, clicked 'Learn More', but it's still a bit confusing. 

 

I think most of the posts in this topic have covered it. Utilizing the API over SMTP is significantly faster. If your community is sending many emails a day, this will help speed up your site. 

I've developed an integration application that will allow your IPB community to send emails via the AWS SES API. I will release it to the marketplace however looking for some folks to test it. Please send me a PM if interested.

Application has been released!
 

As long as the AWS Access Key has the right policies attached, yes you can use the same credentials. It comes down to more user preference. I typically sort my credentials by service so I can rotate them individually. That way if your Wordpress installation is compromised, IPB will remain safe. Also, you may attach different policies for IPB than for Wordpress which helps you keep each credential with the least amount of access as possible. 

Service refers to the software being used in this case. So in AWS, you will have a Wordpress user with their own credentials and a separate IPB user with their own credentials. 

Application has been released. 
 

Service refers to the software being used in this case. So in AWS, you will have a Wordpress user with their own credentials and a separate IPB user with their own credentials. 

Service refers to the software being used in this case. So in AWS, you will have a Wordpress user with their own credentials and a separate IPB user with their own credentials. 

Purchased, thanks!

Good news! Application has been released!
 

Application has been released!
 

Ubuntu 18.04 LTS is always a very stable option. Very widely supported and EOL in 2023 with maintenance/security patches out to 2028. Ubuntu 20.04 just came out this year yet and is making its way into mainstream although I see 18.04 more widely used.
Plesk offers a free option for their control panel software that supports 3 domains before needing to upgrade. I personally like it more than WHM/cPanel. More intuitive and user friendly. 

@Chris Anderson, all valid questions. The application is extremely light weight. At this point, we are only overriding 2 functions to introduce the functionality. Having said that, as IPB changes and updates are made, this makes it extremely easy to update alongside IPB. IPB devs has already done the leg work in developing the application to be easily extended. This is how they have already integrated Sendgrid, SMTP, PHPMailer etc. These are all extensions of their base Email class. To be honest, I am surprised they have not included many other email service options as it was very easy to build in this functionality.
Second, this application is built on AWS's open source PHP SDK which is heavily supported and has a very large audience. 
Third, we have a fairly large audience in the applications we've developed with over 1000 clients having used our services. 
Lastly, and in all reality, I wouldn't be too worried. I am confident IPB will introduce this functionality natively in the future as they already work with S3. All it takes is for a community to rely heavily on a third party application for them to introduce it into their core application. Thanks for the questions!