May I ask if this is the automated email comes from AWS SES?
Yes it is.
Then as a current workaround, do you have anyway to change the subject/address of the automated email?
I will ping Pipedream engineer to triage it, but couldn’t guarantee the duration of the fix
I cannot change anything of this notification. I have done my research and rewrite the code to v2 and try to get all possible supporting materials. Please fix it asap. Meantime, can you let me know what is the spam email policy at your end? Do you have blacklist policy? I only know there is a file size limitation of attachment.
Hi , I don’t think there’s a spam policy in place. I think only Pipedream engineer will have more details, I will ping him and post the update here asap.
May I know if you forward this issue to Pipedream engineer already? Thanks.
I’ve already forwarded 
Hi thanks for the bug report.
I’ve gone ahead and created a public issue for this so it’s tracked for triage:
You can subscribe to that issue as well as add comments to it for more context/background information.
Hi - I recently stumbled upon a specific AWS trigger for inbound SES emails, maybe trying this will help?
It’s specifically built for inbound SES emails, I wonder if that is built specifically for this use case
Noted I will give it a try.
Hi, just to add a little bit information here. I have trouble receiving emails from sender address: ‘MAILER-DAEMON@eu-west-1.amazonses.com’ and subject:’ Delivery Status Notification (Failure)'. But if the subject changes to others even with the same sender address - the email receiver trigger works fine. Not to mention my trigger worked just fine 3 months to 11 months ago - meaning my codes parse sender and subject information and do the rest of things. So logically the issue occurs at the pipedream’s end. Maybe some hidden changes were made.