amazon-ses

问题 I am trying to write a Lua library for Amazon SES that will allow me to send API requests. I've poured over the documentation and various examples but I am continuing to get the following error: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. One of my functions somewhere along the line is formatting data incorrectly or doing something to cause the end result of

问题 I want to create a RAW-Email inside my iOS-App. Looking to the documentation, I need to encode my message to MIME-Standard, but I'm not so familiar with this topic. In the documentation there is also example-code for python and java. How can I achieve this in SWIFT? func sendRawMail(){ let sender = "sender@mail.com" let recipient = "recipient@mail.com" let rawMessage = AWSSESRawMessage() // rawMessage?.data = "I guess HERE I have to put the MIME- Data?!" let rawRequest =

问题 What would I return from a Java SES receiving lambda to cause the rules to stop? AWS provide examples in Node, but what would this look like in Java? https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-action-lambda-example-functions.html exports.handler = function(event, context, callback) { ... // Stop processing rule set, dropping message callback(null, {'disposition':'STOP_RULE'}); } else { callback(null, null); } }; How would I do this with the Java SDK though?

问题 Due to a bug in our application, one of our testing servers started spamming mail orders to AWS SES. We believe that these mails have been put into a queue, as the mail receiver keeps getting around 1 - 2 mails per second, and is not stopping. The SES console doesn't show real time sent mails, so we are still figuring out how many mails have been sent to the queue. Is there a way to stop this behaviour? We use the same SES for the production application, and we fear we might runnout of mails

问题 I have a gmail account linked to my domain account. AWS SES will send messages to my S3 bucket. From there, SNS will forward the message in a raw format to my gmail address. How do I automatically convert the raw message into a standard email format? 回答1: The raw message is in the standard email format. I think what you want to know is how to parse that standard raw email into an object that you can manipulate so that you can forward it to yourself and have it look like a standard email. AWS

问题 Requirement is to send templated mail based on received bodydata from api. BodyData may not contain some tags. see below sample Template part. <p>{{sender}} has invited you to join team {{teamName}}</p> so body data may not contain teamName. So I want to put if condition on {{teamName}} in template. Please help me here to find solution 回答1: For conditional logic in an SES template you can use if else statements like you would in code. For your example you would use something like <p>{{sender}

问题 I am currently exploring storing the attachments of an email separately from the .eml file itself. I have an SES rule set that delivers an inbound email to a bucket. When the bucket retrieves the email, an S3 Put Lambda function parses the raw email (MIME format), base64 decodes the attachment buffers, and does a putObject for each attachment and the original .eml file to a new bucket. My problem is that this Lambda function does not trigger for emails with attachments exceeding ~3-4 MB. The

问题 I am currently exploring storing the attachments of an email separately from the .eml file itself. I have an SES rule set that delivers an inbound email to a bucket. When the bucket retrieves the email, an S3 Put Lambda function parses the raw email (MIME format), base64 decodes the attachment buffers, and does a putObject for each attachment and the original .eml file to a new bucket. My problem is that this Lambda function does not trigger for emails with attachments exceeding ~3-4 MB. The

问题 I am currently exploring storing the attachments of an email separately from the .eml file itself. I have an SES rule set that delivers an inbound email to a bucket. When the bucket retrieves the email, an S3 Put Lambda function parses the raw email (MIME format), base64 decodes the attachment buffers, and does a putObject for each attachment and the original .eml file to a new bucket. My problem is that this Lambda function does not trigger for emails with attachments exceeding ~3-4 MB. The

问题 I am currently exploring storing the attachments of an email separately from the .eml file itself. I have an SES rule set that delivers an inbound email to a bucket. When the bucket retrieves the email, an S3 Put Lambda function parses the raw email (MIME format), base64 decodes the attachment buffers, and does a putObject for each attachment and the original .eml file to a new bucket. My problem is that this Lambda function does not trigger for emails with attachments exceeding ~3-4 MB. The