I don't have any technical problems, but I have a question that I would like to be answered out of curiosity.
Here is my current understanding of how email works:
One of the privileges of having your own domain is that you can hook it up to IMAP/POP3/SMTP servers and use them to send and receive messages to and from "anyone#yourdomain.com". With spam being such a problem, however, the SMTP server that you use to send messages must add a bunch of headers (DKIM, SPF, etc) to each message that you send in order to prove that the SMTP server has the authority to send emails from that domain. The receiving SMTP server can cross-check those headers with DNS records that it finds to verify the legitimacy of the email message.
So if you want to send emails with your domain cheaply, you can use Gmail's "Send Mail As" feature. I followed this help article to get mine working: https://support.google.com/domains/answer/9437157
Note: I unchecked the "Treat as an alias" option during the setup.
But wait... no additional DNS configuration required? I have my domain registered with Cloudflare, and there are no entries related to Google in there.
There is this step in the setup process:
But it seems that this only for Google to prevent you from using their servers to send spam. What is stopping Google from impersonating any email address they want? Why do receiving SMTP servers trust an email from "anyone#yourdomain.com" if Google's SMTP servers have no way of adding legitimate SPF/DKIM headers?
The short answer is that nothing prevents Google from doing this, and that DMARC was created for exactly this case.
There is nothing that stops Google from impersonating any domain. However, there are things receivers can (and should) do when they receive an email which isn't send from the server indicated in the From: field.
Try sending an email from the alias you just added to a different #gmail.com inbox. You will see that it says via gmail.com behind the sender email address. But other email receivers might do more: flag this message with red exclamation marks and scam warnings, throw it into spam or even deny receiving it completely. Gmail probably has some hardcoded trust, but try doing this from your own SMTP server and the above will very likely happen.
As you say in your question, you can authorize your emails by marking gmail.com as an authorized sender with SPF (which protects against forging from other domains, but doesn't stop Google), or even sign your emails with DKIM (not possible from Gmail UI, but you can do this in some email clients or send email with a custom Python script like me; Google can't do this without knowing the key).
However, that only solves one side of the problem – authorizing legitimate email messages. But what if an SMTP server still receives an unverified email? What if they have previously received an email from the same sender which was DKIM signed? What if DKIM passes, but SPF fails?
Because the behavior in that case is largely unspecified, and also the sender wants to check if their DKIM/SPF authorizations are actually working, and if anyone is attempting to spoof them, another standard was created: DMARC. It introduces another DNS TXT record where you can say what checks are required to pass, what to do if they fail, and also what basic analytics should the receivers report to the owner of the domain.
Of all webmail client providers, Google's Send mail as is actually the most well-implemented for a variety of reasons.
First of all, how it works is not different from when you set up POP3 or IMAP using a mail client like Outlook or Thunderbird. You have to specify the domain and port where you receive emails from, and the domain and port where you send emails from. For example, Google's incoming and outgoing servers for IMAP are as follows:
imap.gmail.com:993
smtp.gmail.com:465
The Send mail as feature is a partial implementation of that. It only implements the outgoing part.
How mail clients like Outlook and Thunderbird send emails, is basically that it sends the email to the outgoing mail server, and the outgoing mail server then sends the email. Usually, outgoing mail servers will require some sort of authentication, and will allow authenticated users to only send from specific email addresses.
Gmail works the same way. The outgoing mail server is the one that has to pass the SPF and DKIM tests, not Google's servers.
No other webmail clients do this. Hotmail used to do this, but they recently removed the feature. Now, the option is very difficult to find, and they just rewrite your FROM address and sends your email from Hotmail's SMTP server, which creates delivery problems.
They don't provide you with the option to send emails from another SMTP server, because this allows people to very easily set up virtual mail servers that can send emails under a domain of your choice, but use say a typical free Hotmail account to store incoming mails. This takes away business from their paid services, because both Hotmail and Gmail sell the option to host your company emails. I'm sure Google also knows about this, but it is really awesome of them to still keep the option available to free Gmail users.
If you want to learn more about virtual email servers, you can check out this article here: https://blog.terresquall.com/2022/01/setting-up-a-virtual-postfix-mail-server-part-1/
Configured Zabbix server to monitor websites if status code 200 is ok or not. I did created also the triggers and actions like you can view in the screenshots but so far still no email notification at all, email server work ok.
Configured Trigger
Configure Actions
Any though on this?
Thank you in advance
You need to set up your SMTP server settings, add the recipient email in the desired user's media and configure an action accordingly.
The quickstart guide covers all the required steps.
we have an application that is using the Outlook REST API v2 to allow the users to send emails from the app.
Today one of our clients send us a bug report, that after they created a new Office365 account for their company they can't send emails through our app. The current case was for sending email to hotmail.com account. The email bounces back with error code
550 5.7.708 Service unavailable. Access denied, traffic not accepted
from this IP.
The user also reports that they are able to send the same email from the Outlook web client.
I have found this issue on the network: https://social.technet.microsoft.com/Forums/ie/en-US/608d046b-755a-4264-8cdd-fc34c72ccf8f/office-365-tenant-blacklisted-on-all-emails-sent-by-ms-outlook-2016?forum=onlineservicesexchange and am now wondering if this is just a bug on Outlook side or we have missed something on our end?
You have to go here: https://sender.office.com/ and put the incriminate ip to delete it from the list.
Please help .I have configured my outgoing email settings in sharepoint properly but still facing the same issue. Can any one help so it will be a pleasure.
I have created a document library in sharepoint 2007 and i have enabled incoming email settings to the doc library. When I am trying to send an email from workflow I am getting the error...
System.Net.Mail.SmtpFailedRecipientException: Mailbox unavailable. The server response was: 5.7.1 Unable to relay for EmailDocLibrary#xxx.com
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at DP.Sharepoint.Workflow.Common.SendMailWi
Do i need to setup anything before sending an email. Please help me.
Thanks
Your outgoing mail server isn't setup for relaying from just any address. Checkwith your email server adminto make sure that you are able to send outgoing messages with the email address you have.