Please help.
I ve been stopped for a week on a problem. I read articles and forum, there is no clear solution.Several people had similar issue, but no common solution if any,
"reason: 554 Message rejected: Email address is not verified. and "DNS 5.0.0 Service unavailable
Objective: I do just wish to be able to use "sendmail" from PHP. This is working (only via my gmail account gmail.com credential on my Windows Laptop) but partially on the Linux AWS server. (only to gmail addresses) .
I do not wish to become an "email admin", and thought "SES" was the simplest solution, so I followed the instructions. I wish to avoid using and downloding the SES API, aging just with to run basic "sendmail" commands from PHP.
To remove the PHP potential and do basic: I tried a simple command from the unix prompt (i.e. "sendmail -t < testfile.txt") , it is failing (for same reason as via PHP) because of this:
reason: 554 Message rejected: Email address is not verified.
=================================================
command run at the prompt (ec2-user)
sendmail -t < mail_gmail_to_Celox.txt
-----the file contains:
to: francois.picard@celoxica.com
from: picard.fx@gmail.com
subject: test run with AWS prompt
This is a body test, using from my gmail.com
I ve tried different addresses, (to and from), I always get a similar error
LOGS in /var/log/maillog:
Feb 28 15:28:15 domU-12-31-39-02-C8-39 sendmail
3895: q1SFSFJF003895: from=ec2-user, size=152, class=0, nrcpts=1,
msgid=<201202281528.q1SFSFJF003895@domU-12-31-39-02-C8-39.compute-1.internal>, relay=ec2-user@localhost
Feb 28 15:28:15 domU-12-31-39-02-C8-39 sendmail
3896: q1SFSFcL003896: from=<ec2-user@domU-12-31-39-02-C8-39.compute-1.internal>, size=427, class=0,
nrcpts=1, msgid=<201202281528.q1SFSFJF003895@domU-12-31-39-02-C8-39.compute-1.internal>, proto=ESMTP, daemon=MTA, relay=localhost
http://127.0.0.1
Feb 28 15:28:15 domU-12-31-39-02-C8-39 sendmail
3895: q1SFSFJF003895: to=francois.picard@celoxica.com, ctladdr=ec2-user (222/500), delay=00:00:00,
xdelay=00:00:00, mailer=relay, pri=30152, relay=
http://127.0.0.1 http://127.0.0.1, dsn=2.0.0, stat=Sent (q1SFSFcL003896 Message accepted for delivery)
Feb 28 15:28:16 domU-12-31-39-02-C8-39 sendmail
3898: q1SFSFcL003896: to=<francois.picard@celoxica.com>, ctladdr=<ec2-user@domU-12-31-39-02-C8-
39.compute-1.internal> (222/500), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=120427, relay=
http://127.0.0.1 http://127.0.0.1, dsn=5.0.0, stat=Service
unavailable
Feb 28 15:28:16 domU-12-31-39-02-C8-39 sendmail
3898: q1SFSFcL003896: q1SFSGcL003898: DSN: Service unavailable
Feb 28 15:28:16 domU-12-31-39-02-C8-39 sendmail
3898: q1SFSGcL003898: to=<ec2-user@domU-12-31-39-02-C8-39.compute-1.internal>, delay=00:00:00,
xdelay=00:00:00, mailer=local, pri=31728, dsn=2.0.0, stat=Sent
=====================================================
this is what i did for set-up (i followed
http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/InitialSetup.Customer.html)
1) Setup of Ammazon SES
-Verifying Email Addresses
-Requesting Production Access
I also have productions access
- From the "AWS mgt console", the "Verified Sender Email" (send test mail" works fine
2) SMTP Credentials
generated and saved these credentials
3) Integrating with Your Existing Email Server
- "Setting Up a Secure Tunnel"
then
==================================================
May be there is an obvious set-up issue ?
QUESTIONS:
Q1) NOTE: I did NOT do this "Authenticating Email with SPF" or "with Sender ID"
http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/SPF.html
I've bought a domain name via 1and1.co.uk, and then they have a simple GUI to assign it to my "AWS IP address".
NOT sure where to add these records????: "spf2.0/pra include:amazonses.com ?all"
could this be cause of the error "Email address is not verified" ??
Q2) On the AWS server, before I configured it to be "SES", I was able to send emails, but ONLY the ones with recepints to "xxx@gmail.com" was working.
For other domain (say orange.fr) I was getting "DSN: Data format error"
Hence why I wanted to try SES
Q3) no-reply@mydomain
Assuming a solution is found and emails can be sent, I then wish to send email as from: no-reply@mydomain, but I think I would need to confirm that address too,
https://console.aws.amazon.com/ses/home#verified-senders: "Verify a new sender" expect one to get the email to confirm an address, which does/will not exist on my domain.
is there a way around this ?
Many many thanks.