- Newest
- Most votes
- Most comments
Based on the error message you're seeing, it seems the issue may be related to the formatting of the email message body rather than the Amazon SES configuration. The "Missing start boundary" error typically occurs when the MIME structure of the message is invalid. A few things you could check:
- Make sure the message body and any attachments are using the correct MIME type boundaries (e.g. multipart/mixed or multipart/alternative).
- Verify the message encoding is set properly, usually UTF-8.
- Check for any special characters or encoding in the message body that could interfere with the MIME structure.
- Try sending a very simple test message with just text/plain body and no attachments to isolate if it's a formatting problem.
It's strange that other sites on the same server are able to send successfully. Some things to cross-check between the working and non-working sites:
- PHPMailer or library version in use
- Message body/attachment formatting
- IAM permissions for the API keys
- Network connectivity/routing between server and SES
Let me know if simplifying the message structure or comparing configs between sites provides any clues. Sometimes minor differences in message formatting can trigger errors. Happy to provide code samples if needed.
While that was in the transcript, I originally thought that it had to do with something about that. In my testing I created a 2nd set of credentials to test and those didn't work. So I continued going down a rabbit hole. Kept seeing it also say credentials not correct. I finally fully deleted the existing creds for that system and then created new ones and it started working again. No msg stating that creds started failing or that they had been deactivated.
Relevant content
- Accepted Answerasked 2 years ago
- Accepted Answerasked 2 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
For some reason the user that was still active in the system some how stopped working. After recreating for a 3rd time the new credentials finally started working for this. Why they where working one day and stopped the following day I do not have an answer for this. Nothing in the system said that the credentials shouldn't have worked.
Anyone have any thoughts?