PaulCooperSDC Posted April 17, 2020 Posted April 17, 2020 Hi all, We've just come across an issue where SLC are sending some of their emails through a service that uses randomised AWS email addresses eg 01020171826d09a-b818401e-1aed-42b3-b543-d6c8925eac7e-000000@eu-west-1.amazonses.com Some of these are getting blocked by our email filter. These emails are tied into providing logins for college staff to access the SLC's HE portal. I'm really against whitelisting the whole domain, and I don't want to have to manually dredge through all emails from eu-west-1.amazonses.com to find the relevant emails. What are you doing to mitigate this? Thanks Paul
FishCustard Posted April 17, 2020 Posted April 17, 2020 Why in the name of sanity would anyone do that? That sounds like a bug on the SLC's end - I'd report it formally and manually release until they fix it.
PaulCooperSDC Posted April 17, 2020 Author Posted April 17, 2020 Why in the name of sanity would anyone do that? That sounds like a bug on the SLC's end - I'd report it formally and manually release until they fix it. That's what we've done and the SLC are looking into it. In the meantime we're going through our message queue daily, filtering on the AWS domain and looking for any SLC emails that are blocked, reviewing 'just in case' then releasing. Bit of a pain and not really sustainable but it is what it is.
SimonHooker Posted April 21, 2020 Posted April 21, 2020 It sounds like they are either moving their email sending to SES, or have misconfigured something. By default SES send through the *.amazonses.com domain unless you have set up a validated Domain that's set up just right. I'm sure that they'll sort it out soon enough though.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now