YOU@YOUR-DOMAIN.COM – This can be any email address to which you need DMARC reports sent. Mail providers sent you report on this, that you can review to make sure no one sending spam mails.
When sending email from postfix mail sever that use mailgun for relaying mails, i get error
Jan 4 03:16:06 serverok-vm postfix/qmgr[22652]: 795731A8D: from=, size=820, nrcpt=1 (queue active)
Jan 4 03:16:06 serverok-vm postfix/smtp[24050]: warning: SASL authentication failure: No worthy mechs found
Jan 4 03:16:06 serverok-vm postfix/smtp[24050]: 795731A8D: SASL authentication failed; cannot authenticate to server smtp.mailgun.org[34.237.7.101]: no mechanism available
Jan 4 03:16:06 serverok-vm postfix/smtp[24050]: warning: SASL authentication failure: No worthy mechs found
Jan 4 03:16:06 serverok-vm postfix/smtp[24050]: 795731A8D: SASL authentication failed; cannot authenticate to server smtp.mailgun.org[34.232.180.42]: no mechanism available
Jan 4 03:16:06 serverok-vm postfix/smtp[24050]: warning: SASL authentication failure: No worthy mechs found
On checking postfix mail queue, the mail is stuck in queue
root@serverok-vm:~# postqueue -p
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
795731A8D 820 Wed Jan 3 21:38:20 postmaster@mailout.serverok.in
(SASL authentication failed; cannot authenticate to server smtp.mailgun.org[54.164.235.211]: no mechanism available)
info@serverok.in
-- 1 Kbytes in 1 Request.
root@serverok-vm:~#
The problem is fixed by installing libsasl2-modules.
Many cloud hosting providers, including Google Cloud, AWS, Microsoft Azure, and DigitalOcean, do not support sending emails directly from their servers. They often recommend using a third-party SMTP service for sending emails. Third-party SMTP servers enhance email deliverability and eliminate the need to manage your own email server. When hosting on a shared server, email deliverability can be compromised if another user sends spam, resulting in your IP address being blacklisted. Using a third-party SMTP service ensures consistent email delivery without these risks.
Below is a comprehensive list of top third-party SMTP service providers ideal for sending emails from your website.
Smtp2Go
SMTP2GO is a reliable and scalable email delivery service that provides a robust SMTP server infrastructure for sending emails from anywhere in the world. They offer a free plan for up to 1,000 emails per month, as well as paid plans starting at $15 per month for 10,000 emails.
$0.10 per 1,000 emails sent. Free tier customers receive up to 3,000 message charges free each month for the first 12 months after you start using SES.
Disadvantage: You can only send from @your-domain.extn, if you have a SAS application and need to send it from some other email address, you need the domain added to SES and verified.
To get your Amazon SES service activated, you need to contact Amazon support. Verification is a manual process, can take up to 24 hours. You need to give them information about your use case, how you prevent spam, and how you handle email bounces.
No more free plan. Price starts at $0.5 per day + $0.1 per every 1000 emails.
How much do you have to pay per month if you sent 1000 emails per month?
Answer: Based on the information you shared, you will be paying $15.10 for 1 month. The amount is broken down to $0.10 for 1000 emails and $0.50 x 30 days = $15.00. This is why the total is $15.10. The daily $0.50 is charged to your account regardless of whether or not you will be sending emails.
