Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-content/plugins/wp-optimize/includes/class-updraft-smush-manager.php on line 1215

Deprecated: Creation of dynamic property WPO_Page_Cache::$rules is deprecated in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-content/plugins/wp-optimize/cache/class-wpo-page-cache.php on line 99

Deprecated: Creation of dynamic property WP_Optimize_Minify::$minify_commands is deprecated in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify.php on line 16

Deprecated: Creation of dynamic property WP_Optimize_Minify::$enabled is deprecated in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify.php on line 22

Notice: Function register_block_script_handle was called incorrectly. The asset file for the "editorScript" defined in "contact-form-7/contact-form-selector" block definition is missing. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/functions.php on line 5827

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vol9_8/epizy.com/epiz_21441008/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Forward emails to multiple recipients in Google Apps – Rajib's Blog Rajib's Blog

Forward emails to multiple recipients in Google Apps

Forward mails to more than one recipient in google apps

Forward mails to more than one recipient in google apps

For reasons best known to Google, the email component of Google Apps allows users to automatically forward all email to a single email address only. Since it is not uncommon for organizations to set-up a common email ID for interacting with customers and then forwarding all email received to multiple people for action, the restriction on forwarding emails to multiple recipients is a bit of a bummer.

Sure, multiple recipients can use the ‘recent:’ tag while logging in and ensure that all of them download the emails, but it is easy enough to forget to switch on ‘Leave messages on server’ and actually delete all messages.

Recently, a friend of mine also complained of this and since he is an individual, yet affected by this issue; I felt I should figure out a workaround to this and publish it.

Create Email Groups in Google Apps

Create Email Groups in Google Apps

The simplest solution is to set-up an Email Group in google apps. Simply put, an email group is an email ID that itself comprises of multiple users. Any email sent-to the group ID is automatically replicated to all members of the group.

The solution to forward emails to multiple recipients simply consists of creating a group-ID and adding recipients to the group. Once added, configure the master account to forward emails to the group-ID and they will be forwarded to all the recipients.

To illustrate the concept:

  • Let us assume that we have a real-estate project called ‘Lotus Leaf‘ and we have an email ID lotusleaf@trustedbuilders.com on which we encourage prospective customers to shoot enquiries.
  • The organization requires that all emails received at lotusleaf@trustedbuilders.com should be forwarded to director@trustedbuilders.com, marketing@trustedbuilders.com, accounts@trustedbuilders.com & support@trustedbuilders.com.
  • To achieve this, we will create an email group called team-lotusleaf@trustedbuilders.com and add the email IDs of the four persons to the members list.
  • Now we configure POP & Forwarding options of lotusleaf@trustedbuilders.com to forward all emails to team-lotusleaf@trustedbuilders.com
  • All emails received at lotusleaf@trustedbuilders.com will now be automatically replicated to the members of the team-lotusleaf@trustedbuilders.com group

Notes:

Add Users To Email Groups In Google Apps

Add Users To Email Groups In Google Apps

  • If creating a group, try to set the group type to “Team”. In this mode, you can add recipients from any domains. For ex: Group members can be from Hotmail, Yahoo, Rediff or any other email service.
  • In “Team” mode, emails received at the group ID are automatically forwarded to the team members who can be from any domain.
  • Any member of the team can send an email to the group ID and the mail will be replicated.
  • Non group members cannot send emails to the group ID since their email will be rejected instantly. This is useful to avoid spam.
  • If a group member forwards a spam message to the group ID, it will be replicated to all the group members. Please avoid blindly forwarding every email to the Group ID; instead use a rule to forword emails so that only those emails which concern the group are forwarded.

You may also like...

7 Responses

  1. Julie says:

    Thanks for this post – it was mega-helpful. Not sure why Google decided to make it this hard?!

  2. What if I want to forward to multiple addresses outside my main domain?

    Like info@corinteractive.com –> forwards to: corinteractive@gmail.com and cfechner@yahoo.com

    • Rajib Ghosh says:

      Hi Cory,

      Google Apps allows you to add other domain email IDs to the group.
      Your will have to set the Group’s permissions correctly to allow other domain email IDs to also sent messages to the group ID.
      If you only want one-way traffic (from Group to Users), then the ‘Announcement Only’ setting will work fine.

      HTH

  3. Colin says:

    Is there a way to make and existing email address have more recipiants ? obviously it should have been setup like the above in the first place.

    info@test.com is sent to a@test.com and b@test.com and c@test.com

    but if c@test.com wants to see emails to a@test.com aswell as info@test.com , would i have to delete a@test.com and create a group a@test.com ?

    sorry for the confusing post.

    • Rajib Ghosh says:

      Hi Colin,

      It appears that Google has not yet added the facility to forward emails to multiple recipients and still requires the use of Google Groups to forward messages.

      HTH

  4. Nick says:

    Groups don’t appear to be working correctly for me. I create a group and add myself as a member. When I email the group – I never receive my test email.

    Is this a known bug or is there a trick to this? Seems pretty straight forward.. but, again, it’s not working.

    Thanks

  5. Will says:

    Nick, I think if you are the one sending the message, you won’t receive your sent message but the other recipients in the group e-mail address that you belong to will.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.