First, I changed the admin email address with my email address for testing purpose. Then later I changed back to the original. But the problem is, now the new user registration email comes from my email address to admin email address. I am confused as to how dnn is taking my email address as the sender email address. Can anybody point out how the sender email address is configured in dnn in this case?
I have searched through various dnn community sites. But I haven't found an answer to my question.
I think your account is linked as the Administrator acount of the portal.
Go to Admin > Site Settings.
On that page select the tab Advanced Settings. There you will find the Security Settings. Change the Administrator account there. THat account will be the sender of the portal mails.
Related
My client wishes to bring his website down and domain down permanently and delete all of these accounts. Hosting and domain are handled by HostGator. WordPress theme has the info#domail.com reference. His email is a gmail account. The problem is, he wants past customers who have been using info#domain.com to be redirected to his gmail account username#gmail.com. I tried using just the domain as a redirection tool, but it only seems to redirect to a different websit.com, not an actual email account. Is this possible? How would I do this for him? Thanks for whatever help or info anyone can offer.
--jerry
I am implementing an email verification service, with the purpose of confirming that the person registering is indeed the owner of that email address (specifically, that they work at the organisation that the email domain belongs to).
I will send an email post-registration with a single-use link in it that will set their status to verified = 1.
Users can choose to register and log-in using either a simple email/password combination, or by using the Google Sign In service.
My question is: do I need to verify the ones that have registered with Google Sign In? In order to provide their email address to me, they had to sign in with Google, who then confirmed the address. Is there anything I've missed here, or can I immediately consider these users to be the verified owners of these addresses?
If you are using google sign in there is no need to verify the user.
Whereas if have your own login system, then you must verify the email because
if the email is not verified then you cannot have forgotten password feature through email
and also the user might not have actually had the email so anyone else could create the same email and if you have forgotten password through email someone else could easily access others data.
Websites will often send notification emails from addresses like hello#example.com or no-reply#example.com. When these show up in Gmail / Inbox, they often have a name and an avatar associated, like this one from Zeplin:
I know if you're using Google Apps, as an administrator you could create a user called no-reply and set their avatar. But this also uses up one user slot which costs $5 / month. And I'm not sure if this technique works outside of Gmail or Inbox.
Are there other ways to set the avatar for automated email addresses?
Have a look at Gravatar.
What Is Gravatar?
An "avatar" is an image that represents you online—a little picture
that appears next to your name when you interact with websites.
A Gravatar is a Globally Recognized Avatar. You upload it and create
your profile just once, and then when you participate in any
Gravatar-enabled site, your Gravatar image will automatically follow
you there.
More info here:
https://en.gravatar.com/
This is the result for the email above.
A catch all email address allows you can receive the Gravatar activation emails for non existent email addresses.
Details for Google Apps:
Google Admin console
From the dashboard, click Apps, then click G Suite
Gmail
User settings.
Catch-all address section
TL;DR Get a verified Google+ Brand Page and enable DKIM authentication for any external service you send email through (ala Mailchimp).
These steps are not documented and Google themselves did not help. But, after implementing them, my business avatar started to appear for emails sent via Mailchimp or Mandrill or some such with a return email address of my domain.
1) Create a Google+ Brand Account page (https://support.google.com/plus/answer/1710600). You may already have one set up as part of general SEO, but you need one for the avatar to work. Make sure too, at the end of the process (which is again, is poorly documented) that on your Google+ brand page, you see the little verified badge next to your business name.
2) Set the avatar you want on your brand page.
3) From whatever external service you send email from, set up DKIM authentication for your domain. Google Inbox won't display an avatar if it detects the email as being sent 'on behalf' of your domain; the DKIM authentication will make Inbox believe your domain actually sent it, and then apply the avatar. (These instructions vary wildly depending on your email provider, but here are the ones for Mailchimp).
Go to https://myaccount.google.com/email
Click on "Advanced Settings" then on "Alternate Email".
Verify emails.
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.
Shame on me. :(
I forgot where I configured the E-Mail account used in my Drupal site.
I guess I set up the E-Mail with the installation of Drupal, could that be possible?
Does Drupal care about registering the E-Mail address and getting incoming mails?
I get all the mails at this address forwarded to my private E-Mail address, but I really don't know where I registerd the drupal address and where I told Drupal to forward mails to my private address.
In the Drupal dashboard I can't find settings for an E-Mail Account.
Drupal 6 site email is stored at 'Site Configuration' -> 'Site information' (admin/settings/site-information).
Drupal 7 is stored at 'Configuration' -> 'Site Information' (admin/config/system/site-information).
Drupal does not handle receiving emails or forwarding emails. This setting sets the from address for most generic site emails (new account, forgot password, etc). You must have configured the forwarding through your mail hosting provider.