Member Avatar for complete

I have my fresh Drupal 7 web site up and running. I am currently testing it. My first test is to try the functionality of creating a new user. I tested added myself (no, not my admin account -- a different one with a different email address). The new user's (mine) email got an alert saying that the account would be approved by the admin and further instructions and password would be sent to me.

I got the alert email also at the admin email address and I logged on and assigned the account a password and approved the account.

But the new user's email never got the notification. I also tried to find the user's email address by using the admin's privileges on the site in case I needed to deliver the message to the user by hand. But I could not find out how to do that.

Please help and advise.

  • 2 Contributors
  • 2 Replies
  • 238 Views
  • 19 Hours Discussion Span
  • Latest Post Latest Post by complete

Dani AI

Generated

Short expert summary tied to the thread: as suggested, the missing user notification often winds up in the recipient's spam folder — which confirmed in this case. That behavior is common when a site sends mail with the default PHP mail() path or without proper DNS authentication (SPF/DKIM/DMARC); major providers (Gmail) explicitly recommend authenticating sending domains to avoid spam/quarantine. ()

Practical fixes (quick checklist). Use a site address at the website domain for the site mail account (avoid sending from free providers such as gmail.com). Replace PHP mail() with an authenticated SMTP sender by enabling the SMTP Authentication Support module and manage mail backends/formatting with Mail System — this gives control of the envelope/from headers and lets the site send through a real SMTP account or a transactional provider (SendGrid/Mailgun/SES) for much better deliverability. (drupal.org)

Debugging and verification. The admin user list (People → List in Drupal’s admin) shows registered emails and allows editing/setting a password if manual delivery is needed. For delivery problems, capture or inspect outgoing headers (Gmail: “Show original”) to check the Authentication-Results (SPF/DKIM) and any 5xx/4xx bounce codes. For local troubleshooting, use a mail-logging module (Maillog) or server mail logs to see the raw messages and headers; note Maillog may record sensitive content and should be used with privacy/country-law caution. (hostarmada.com)

Short operational notes: start by switching the site-from address to a domain email, publish correct SPF/DKIM (and DMARC for higher volumes), and send test messages via the SMTP module or a transactional provider before going live. For sites sending significant volumes, register and monitor with Google Postmaster Tools and keep spam/complaint rates low — following those steps materially reduces Gmail spam placement. ()

Recommended Answers

All 2 Replies

Member Avatar for Member #120589

Did you check the spam folder? Are you sending email from local machine or host server?

Member Avatar for complete

You are right. It was put in the "spam" folder on the gmail account. Good Call!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.