GitLab sends notification emails to the email address I used during registration. Can I change the target email address GitLab uses to send email notifications to?
I've already tried setting/changing my email address on my "Profile settings" but it's used only for display; it doesn't change where GitLab sends notification emails to.
OK it seems I figured out the causing issue.
As it turns out the "Email" property on my "Profile settings" does specify where GitLab sends notification emails. The problem was a bit more elaborate.
There were two GitLab accounts that had the same username! Both belonged to me; one was a regular user and the other was an admin. The two users had different email addresses; just their usernames were the same.
This caused some kind of an anomaly; even though an action was triggered for the admin user the notification email went to the email address of my other user; strange indeed.
I changed the username of one of my users to make them unique. After that, everything worked well.
Hope this will help someone in the future.
Related
I have a Google Workspace (I think that is what it is called) that I use to manage a private email address for a small business.
Everything has been working fine, and I can see the user (richard) in the admin area with associated email set up. I have sent test emails to and from their email account to make sure it is working okay and everything seems to be working fine.
I have two email addresses associated with the domain, for example:
emma#domain.co.uk (me) and
richard#domain.co.uk (richard)
I use the first email address as an admin account, and they use the second one.
They've had this email account for a long time, and have had no problems, however recently they have stopped receiving emails from one sender (their accountant).
I can still send emails to the account from my own personal email address to them, and they are receiving emails from other businesses, but just this one person is sending emails to them and they aren't being received.
Things I've tried:
Checked the spam/junk folders and no emails are there
Checked to make sure the sender isn't on the blocked list
Looked at the email logs as per this suggested article and don't see any record of the incoming email that has been sent
Sent a test email to account#accountant.co.uk and richard#domain.co.uk from emma#domain.co.uk and they both receive my email. When the accountant presses "reply all" the email only gets received by emma#domain.co.uk and never arrives at richard#domain.co.uk
Sent a test email from richard#domain.co.uk to account#accountant.co.uk and she receives the email. When she replies, he doesn't get the reply.
All I can think of is she has somehow blocked him via her email client, but I need to check out all the possibilities of it being a problem at our end as she's not great with email and not sure how I'm going to navigate that one :)
Any suggestions welcome!
I am new to firebase and I am trying to handle firebase user authentication in React.js. I did manage to create users with email and passwords. But, now I would like to send the user an Email link to reset their password.
My code currently look like this.
// This line of code belongs to the top
import { auth } from '../firebaseConfig'
//This part goes under the React component
<p onClick={async () => {
try{
await sendPasswordResetEmail(auth, // My Email Id)
alert('Password reset link has been sent to your email')
}
catch(err){
alert(err)
}
}}
>Forgot your Password ?</p>
However, I do not get any error messages and I do get the alert message that says "Password reset link has been sent to your email." Unfortunately, I didn't receive any email. Note that I have given my own email id as the parameter for testing purposes.
firebaser here
Did you check your spam folder? We recently see a lot of the emails from Firebase Authentication ending up in the user's spam folder or being marked as spam in a system along the way. This is being tracked in this status message on the Firebase dashboard and in public issue #253291461.
To reduce the chances of the messages getting marked as spam, consider taking more control of the email delivery yourself.
As a first step, consider using a custom domain with your project. Email that comes from a custom domain has less chance of being marked as span.
As a second step, consider setting up your own SMTP server.) for delivering the email, so that the emails are not being delivered from Firebase's shared infrastructure anymore.
While these steps are more involved, they typically will drastically reduce the cases where the messages from Firebase Authentication are marked as spam.
Full Guide Based on Frank's Answer
Firstly create a new email account you can use to relay the Firebase emails through the SMTP server with. I personally chose Gmail, but I tested with Outlook and it also works.
You can now find an SMTP server host that will work for your scenario. If you're sending less than 1000 emails per month you can find free and reliable hosts. I chose SMTP2GO's free option.
Now you've found the SMTP host, add the email address you've chosen as a single sender email (note that if you do own a domain, you can alternatively use that to send emails).
Note that you will have to verify the email, usually by your host sending a link to the email's inbox. Make sure to check spam.
Once verified, navigate to where you host allows you to add SMTP Users and add a new user. This will allocate an SMTP username and password.
Navigate to the Firebase console, and choose the Authentication option from the sidebar (within the Build product category).
Go to Templates → SMTP Settings and enter the details of your SMTP server. The username and password fields are to be filled with the SMTP user login you created in the step above.
It is better to use TLS, but I believe SSL should work too but it is untested.
Click save, and you're all set up - but there may still be steps to perform depending on your email provider.
Provider Specific Steps
If the emails are being sent to an account managed by Google you will have no issues with your emails being quarantined by anti-spam policies and it will work immediately.
If you are using Outlook, you will have a different problem on your hands. Outlook's built in defender will most likely have auto-quarantined your email under multiple policies - that bit is important.
These policies are likely to be both spam and phish policies. If you unblock one of them, the other will catch it and re-quarantine.
Unblock both policies for the email address, and test. You can see the status of quarantined messages in Microsoft 365 Defender app under Review → Quarantine. Please note that you will need to be an administrator to add global allow policies to your email accounts.
If this still doesn't work it is likely that your company has an additional external filter (as mine did), and you will have to add the IP's manually to the Tenant Allow/Block Lists spoofed senders tab.
I've left a company and the email used to access Fabric has been removed.
Now I am working in the same company and they recreated the email with the same handle. I don't know if this is the problem but I'm not receiving any email with reports and I didn't receive the Beta Tester invitation.
My status is active and the interface says that an invitation has been sent. But I'm not receiving anything.
I deleted my user from Organization using another admin account. After that I've invited my user again. No email sent at all.
Mike from Fabric here. The most likely issue is that when you left the company, our mail server recorded a bounce for a no longer valid email address. Even with the address, re-created, our mail server would still have a bounce for the address. I'd recommend sharing your email address or emailing into support(at)fabric(dot)io so we can verify that and clear the bounce if it exists.
I have created a GitHub account and, I do not like sharing my email address publicly (I'm sick of Spam), so I followed GitHub's Keeping Your Email Address Private tutorial and everything worked fine up until the point where you have to verify the fake email you created.
So how do I verify this fake email that I created on GitHub?
I did check my real email account that is associated with my GitHub account incase they sent an email there but no, I have not received anything there. Since it is a fake email address, I thought, maybe I can just click verify, but no, that doesn't work either.
You don't verify the fake e-mail address. This is how it is suppose to work. Just go ahead and use the fake e-mail address with commits.
Update -
GitHub recently update the Keeping Your Email Address Private tutorial. The "Hiding your email for commits on the website" section has everything you need to know, and will credit your commits to you. This way you won't have unverified e-mail addresses anymore.
You don't have to verify your fake e-mail address to use it in commits and have those commits linked to your GitHub account.
You also don't have to create your own fake e-mail address. GitHub creates one for you when you turn on the "Keep my email address private" option on your email settings. Next to your primary e-mail address, you should see a message like this:
Because you have email privacy enabled, joe#example.com will be used for account-related notifications and joe#users.noreply.github.com will be used for web-based GitHub operations (e.g. edits and merges).
You can use that no-reply e-mail address as your fake e-mail address. See the e-mail addresses help page for more details, including information on the new style of fake e-mail addresses that include an id number. Those addresses will continue to work if you change your GitHub account name.
At the moment, we are sending an email address verification email each time someone signs up. This email has been causing a number of problems: people don't get it, they just don't click the link in the email or the email gets block by spam or some other method. We are working on resolving the spam issue, although I don't think it's possible to completely resolve it.
I'm wondering what other methods there might be for verifying and email address. Is there any other way to verify an email address without sending an email? Or is there another method of ensuring people aren't signing up with fake information?
I'm not sure if there are other good methods, but sending an email and having them click a link is definitely the simplest and most accurate.
A main feature to sending that email, is for the person to verify that it's actually them that requested it.
The only way to verify someone owns an email address is to have him use it.
As for verifying users don't enter fake information - not even sending an email can help. With so many disposable/temporary email services out there (like GuerrillaMail) , someone can fill up your form with false info, post a temp email address, log to that address and click the link in your email - manually or programatically.
You have to trust your users to come back for your content, and ignore spammers.
strikeiron.com offers a paid web service to verify if an email exists without sending a message to that email. try it out here is the link: strick
http://www.strikeiron.com/Catalog/ProductDetail.aspx?pv=5.0.0&pn=Email+Verification