epriestley 3dfa89dd5d Update SES API to use AWSv4 signatures ... Summary: Ref T13570. Fixes T13235. In most cases, we use modern (v4) signatures for almost all AWS API calls, and have for several years. However, sending email via SES currently uses an older piece of external code which uses the older (v3) signature method. AWS is retiring v3 signatures on October 1 2020, so this pathway will stop working. Update the pathway to use `PhutilAWSFuture`, which provides v4 signatures. T13235 discusses poor error messages from SES. Switching to Futures fixes this for free, as they have more useful error handling. Test Plan: - Configured an SES mailer, including the new `region` parameter. - Used `bin/mail send-test` to send mail via SES. - Sent invalid mail (from an unverified address); got a more useful error message. - Grepped for removed external, no hits. Maniphest Tasks: T13570, T13235 Differential Revision: https://secure.phabricator.com/D21461		2020-09-15 13:03:49 -07:00
..
__tests__	Use PhutilClassMapQuery instead of PhutilSymbolLoader	2015-08-14 07:49:01 +10:00
aphront	When proxying HTTP repository responses from repository nodes, discard content description headers	2020-04-25 07:51:46 -07:00
applications	Update SES API to use AWSv4 signatures	2020-09-15 13:03:49 -07:00
docs	Update SES API to use AWSv4 signatures	2020-09-15 13:03:49 -07:00
extensions
infrastructure	Fix additional "xprintf()"-class static parameter lint errors	2020-09-08 11:45:48 -07:00
view	When printing timestamps on paper: use an absolute, context-free date format	2020-09-04 16:36:34 -07:00
__phutil_library_init__.php	Delete license headers from files	2012-11-05 11:16:51 -08:00
__phutil_library_map__.php	Update SES API to use AWSv4 signatures	2020-09-15 13:03:49 -07:00