(Archived) How can I send e-mails
You have tried to access an archived page. Please go to the new https://root360.atlassian.net/wiki/spaces/KB to find more documents.
In most cases, sending e-mails is necessary to ensure active customer communication. What are the options to send mail via servers in a root360 environment?
Sendmail() / localhost
The default in many PHP applications is sending via the PHP internal function sendmail(). Sendmail() some other mail programs are installed on every Linux instance.
The e-mails are transmitted by the server itself (localhost) to the responsible e-mail server. It should be noted that the advantages of the flexible AWS infrastructure are used in many spammers. Therefore the IP ranges of AWS are preloaded with a negative SPAM rating for many mail servers.
In addition, AWS monitors the number of e-mails sent in this way and, after an undocumented number, throttles the dispatch for an undocumented period. See also https://docs.aws.amazon.com/ses/latest/DeveloperGuide/limits.html.
This solution is not recommended by root360 as there is no control of the throttling by AWS.
External SMTP server
Sending mail via an external SMTP server as a mail relay is a common option for secure e-mail sending. Please note that AWS monitors port 25 for spam protection and may throttle it.
Therefore, root360 recommends the encrypted transmission via TLS / SSL to port 465 or 587.
AWS Simple E-Mail Service (SES)
AWS SES is a mail relay and has a very good reputation with almost all large mail providers. To maintain this quality feature, each sender domain must be validated by DNS.
Without this validation using SES is not possible. The values for the required DNS entries (http://docs.aws.amazon.com/ses/latest/DeveloperGuide/dns-txt-records.html) are provided by root360 for the desired 2nd-level domains at your request. After successful validation, you can use SES for the validated domain and all its subdomains.
If the DNS entry is deleted AWS blocks the domain within 5 days at the latest.
SES requires encrypted mail (TLS) on port 465 or 587.
Avoiding negative SPAM ratings
The Sender Policy Framework authorizes an e-mail server as the valid sender domain.
Root360 recommends to set a corresponding SPF record ( http://docs.aws.amazon.com/ses/latest/DeveloperGuide/spf.html ) for a smooth shipment .
We are happy to help with the configuration.
root360 Knowledge Base - This portal is hosted by Atlassian (atlassian.com | Privacy Policy)