JustinHawk

As recommended, I'm creating this topic to reinstate the option to download files manually from the Marketplace.
It's bad enough you don't allow the download of apps we purchased when our licence has expired. But, to completely change the way file downloads are handle is a little much.

Please don't get me wrong, I love the idea that we can now do it all with ACP, but you shouldn't disable/change the way that a lot of us download files for localhost setups to test our sites before going live.

Please, please, please allow the option to download files manually like we've done for so many years!
 
(Edit: Happy 600 posts to me, woo!)

We don't have any agreement with Sendgrid. It has simply been implemented for a longer period of time.
There is interest in SES integration (although you can already use SES via SMTP presently anyways). I think the main catch is that they have stricter requirements for handling bounces which would necessitate new functionality being built in, not just slapping in another email gateway and calling it a day. That said, we're monitoring feedback/support for topics requesting SES integration.

I used Sendgrid based on the recommendation of the IPS staff and because support is built into IPS. Unfortunately the price of Sendgrid is 10x that of Amazon's SES simple email service. 
I just switched over to Amazon SES and am stuck using the SMTP route rather than via the API because there isn't native support via IPS like there is for Sendgrid. 
I'd like to ask for or vote for IPS adding support for Amazon SES, just like it supports Sendgrid.

For it to show in the Marketplace, an app/plugin has to be re-uploaded and evaluated by IPS staff before they will allow it through and be visible there.
I can give it a once over and throw it into the Marketplace heap but if it's clear sailing so far you've got no worries I'd guess - this would just be for Marketplace visibility purposes. I'll try to clear this tonight.
I've only got one (two?) things into the new 4.5 Marketplace so far - there's a sliiiiight backlog (my problem actually).
I'll even give @TarunD 's thing a look - double encoding the url would explain a lot of errors away (there still may be Amz specific urls hidden within but thats no big deal to get around) If you have those changes and are willing to share feel free to throw them my way Tarun - save me another code crawl.