Differences

This shows you the differences between two versions of the page.

--- developer_s_reference:administrative_gmail [2025/04/02 17:34] – created adminsteve
+++ developer_s_reference:administrative_gmail [2025/04/03 14:34] (current) – adminsteve
@@ Line 1: / Line 1: @@
 @ageofinsanity.org e-mail addresses
+**TLDR**
+To be included in e-mails going to @ageofinsanity.org:
+For admin@ageofinsanity.org & mud@ageofinsanity.org, join the Google Groups ageofinsanity.org@gmail.com
+To have your own personal @ageofinsanity.org e-mail address forwarded to your person e-mail, reach out to Steve (who will add you to the Namecheap DNS config to enable forwarding for that email address)
 **Default Behavior**
-By default, e-mail going into any @ageofinsanity.org e-mail inbox is automatically forwarded to ageofinsanity.org@gmail.com (forwarding configured in NameCheap; managed by Steve).
+By default, e-mail going into any @ageofinsanity.org e-mail inbox is automatically forwarded to a (Non-Business) Google Groups ageofinsanity@googlegroups.com (forwarding configured in NameCheap; managed by Steve; this group is owned/managed by ageofinsanity.org@gmail.com with password d3@thr0t - note that two-factor notification to Steve's cell phone is enabled because google requires this in order to enable "app passwords" which allow apps like Dokuwiki to authenticate with google's SMTP server).
 **Specific accounts**
@@ Line 9: / Line 15: @@
 mud@ageofinsanity.org - General inbox, used for general communications with the public
-As of now, outgoing SMTP server is not configured, so incoming mail is forwarded to ageofinsanity.org@gmail.com, and responses will come from ageofinsanity.org@gmail.com
+As of now, outgoing SMTP server is not configured, so incoming mail is forwarded to ageofinsanity@googlegroups.com.
 Later, it would be good to have an SMTP server to mail "as" mud@ageofinsanity.org (or any other address within the domain)
@@ Line 18: / Line 24: @@
+{{:developer_s_reference:namecheapemail_redirect.png?400|}}
+**Automated Outgoing e-mails: Wordpress (www.ageofinsanity.org)**
-**Default Behavior**
+Wordpress needs to send outgoing e-mails, and since we do not have an SMTP server yet, it's configured to use Google Cloud API
+The ageofinsanity.org@gmail.com account has a Google Cloud account set up, with the Gmail API set up.  The wordpress site at www.ageofinsanity.org is configured to use this API (through a plugin, WP Mail SMTP) to send outgoing e-mails through Google's API to Gmail's SMTP servers.
+Considerations:  This relies on a 3rd party website to work (https://connect.wpmailsmtp.com/google/), so if this goes out of business, maybe it's time to set up an SMTP server (or expand Namecheap services beyond just DNS, to include SMTP server)
+Notes:  Google API Credentials used to pair Wordpress SMTP plugin with Gmail API (don't share this outside of devs):
+OAuth Client ID:
+142935023046-k9if1m3q66ev8d6ql8quto5ldfacvrsj.apps.googleusercontent.com
+Client secret:
+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
+Created:
+April 2, 2025 at 1:44:46 PM GMT-4
+Instructions referenced to configure plugin: https://wpmailsmtp.com/docs/how-to-set-up-the-gmail-mailer-in-wp-mail-smtp/?utm_source=WordPress&utm_medium=setup-wizard&utm_campaign=liteplugin&utm_content=Read%20how%20to%20set%20up%20the%20Gmail%20mailer#create-app
+**Automated Outgoing e-mails: Dokuwiki (wiki.ageofinsanity.org)**
+Uses Gmail SMTP access using an "App password" generated through gmail.  This is considered not very secure so Google may deprecate the functionality at some point, but it was just the fastest/easiest way to get it set up.
+Once we move away from the app password approach here, we can disable 2-factor authentication on the ageofinsanity.org@gmail.com account to allow us to share access, if there's any want/need.