I need to set up a Chronograf alert for Gmail, but I can't do it.
What I've done are the following steps:
I created a new Alert rules
In the Alert Handlers section I have imported "email" and insert the alert threshold value
I went to edit configuration and set everything as shown in the picture:
configuration for gmail
But when I press the "send test alert" button, no email is sent to me.
I also wrote the body of the email in the "alert rules builder" section just in case. but nothing has changed.
How can I fix it?
Try using less secure apps. log into your gmail account, or https://myaccount.google.com/security
Scroll down to "less secure apps" and enable that. If i recall, gmail blocks apps it considers to be less secure. I had to set this a couple of years ago to use gmail to relay alerts.
Also, your port number is wrong it should be 465 (SSL) or 587 (TLS)
gmail smtp configutation
Related
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.
I want to get email from a specific address (gmail) and automatically create issues. And I'm not sure, how to do this.
In youtrack Mailbox Integration Settings I click Configure New Mailbox Server and then I don't know what to choose. What parameters should I use to get emails from gmail address
Protocol:IMAPS
Host:imap.gmail.com
Port:993
Login:mylogin
Password:mypassword
Select SSL key: nothing
Connection timeout:60
Socket timeout:60
But get [AUTHENTICATIONFAILED] Invalid credentials (Failure)
there is 2 step verification on this account - maybe that can be a reason of the error?
Which exactly steps of verification does the account have?
Here you can find a description of mailbox setup parameters: https://www.jetbrains.com/help/youtrack/standalone/2018.1/Mailbox-Integration.html#enable-mailbox-integration
As of a few weeks ago, I noticed that I am unable to receive emails from my domain account. My application is deployed to the azure server and it uses SendGrid to send emails and this happens from my application. For example my application is 'myapplication.com' and the azure sendgrid configuration for the mail server is set up to use 'Jake#myapplication.com' but when I send and email to my yahoo account, let say to reset my password. The email never makes it, not even going to spam. I remember reading something like this a few weeks back http://sendgrid.com/blog/update-yahoos-dmarc-policy "Yahoo New Policy" but I don't see how that would effect me since my from account is not a yahoo account. If there is no fix for this, what is an alternative email setup
Before considering an alternate email setup, contact SendGrid through support.sendgrid.com, it's possible that Yahoo is wrongly blocking your email. If this is the case SendGrid will advocate for you and work to get it unblocked.
Disclaimer: I am a SendGrid Employee
I'd suggest looking at the sendgrid dashboard and search for that email. You will be able to see exactly what happened.
it seems that Sendgrid IP pool is being deferred by yahoo. I am not sure what Sendgrid is planing to do to rectify this issue as it is impacting their clients who uses shared pool service
I have just stumbled on this issue. And it's not only Yahoo blocking sendgrid emails. They rather complaining about the senders ip address "Send Grid" rather than senders email address. :-(
We are implementing the DocuSign in our application. While signing the envelope in In-Person mode there is an window (popup) to send a copy of the document in an email.
We have entered the email but no email received. Checked settings in the DocuSign portal account but not able to find any setting for this.
Please let us know how to enable the save a copy email in DocuSign.
I would check settings on your side if you are not receiving the emails. Things like security software, spam/junk mail filters, firewalls, etc. that might stop the email from arriving. DocuSign is a widely used platform, if the emails weren't going out it would be publicly known very quickly, and I just tested this myself and I'm getting the emails. I might suggest you call their support department...