I'm fairly new to Magento. Due to a number of conditions, I was given the shop to manage so I'm struggling with some problems. The current one has to do with the password forgotten email. When that option is used, the email never shows up. In the exception.log file, it has something like this
Exception: <ErrorResponse xmlns="http://ses.amazonaws.com/doc/2010-12-01/"> <Error> <Type>Sender</Type> <Code>MessageRejected</Code> <Message>Email address is not verified. The following identities failed the check in region US-WEST-2:
This seemed like an obvious failure with Amazon SES but everything there is working and the address is verified. I finally decided to disable the site in amazon and I removed the DNS entries that were added for it. But with that disabled, the above message still appears.
So I'm guessing that there is some plugin installed that is calling amazon but I've no idea how to find it. In searching the files, I did find the following:
app/code/local/Aschroder/Email/lib/AmazonSES.php
app/code/local/Aschroder/Email/lib/amazonsns.class.php
app/code/local/Aschroder/Email/Model/AmazonSES.php
Would someone please let me know how to troubleshoot this or, at least, how to find the plugin being used?
using community ver. 1.9.2.2
Looks like this extension is installed: https://github.com/aschroder/Magento-SMTP-Pro-Email-Extension
I would imagine that all emails are sent out through this extension as it's a replacement for using the server to send emails.
You could try disabling the extension but that will require the server to be configured with something like sendmail (may already be).
Alternatively, you could look into resolving the verification. Error is mentioned on this help page: http://docs.aws.amazon.com/ses/latest/DeveloperGuide/ses-errors.html
That appears to be the plugin in use but the shop owner is worried about turning it off so he is looking for other solutions. I just wanted to say thanks for the reply and to acknowledge it.
Did you look at the link to the amazon help page that I shared? If you want to stay with the same extension (which should be fine), then your best bet is find a resolution for that error that you were seeing. It was one of the ones mentioned on that page so hopefully shouldn't be too hard to fix.
Thanks for the response and thanks. You're welcome to give one of my replies "Kudos" and accept as solution if appropriate.