Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.
  • 1.  Mail Routing

    Posted 05-05-2019 20:31
    No replies, thread closed.
    Hi

    While setting up the email domain verification it is noted that we are not to use an existing domain within organization. 

    Add this verification record to your domain's DNS settings to verify ownership of your domain. Verifying the domain will allow PureCloud to send outbound emails from this domain.
    Please note this verification process may take up to 72 hours. Be sure not to use a domain that's already being used for email within your organization.

    Can someone please provide some details on this? How does the customer set up inbound/outbound email routing with existing mailboxes that are used to handle interaction with external customer? Is creating a new subdomain the only way to integrate mail routing in Purecloud?

    Thanks,

    MJ


    #Integrations

    ------------------------------
    Mei Jane Lim

    ------------------------------


  • 2.  RE: Mail Routing

    Posted 05-06-2019 20:08
    Edited by Lucie DeCristofaro 05-06-2019 20:08
    No replies, thread closed.
    There are 4 main different ways to configure email in PureCloud. There are highlighted here: https://help.mypurecloud.com/articles/email-routing-scenarios/

    Note that only one of those 4 approaches require that you use MX records. You should be able to use TXT records to verify your domain. Does the documentation imply you cannot add TXT records? We need to fix that, if so - can you send me the link so we can update?

    ------------------------------
    Lucie DeCristofaro
    Genesys - Employees
    ------------------------------



  • 3.  RE: Mail Routing

    Posted 05-06-2019 20:58
    No replies, thread closed.

    Hi Lucie,
    We are going after this method: https://help.mypurecloud.com/articles/register-domain-redirect-inbound-messages/ 

    The warning message appears in the Purecloud Admin>Email setting under Edit mode. I've attached the screenshot for your reference.
    It implies that we should not use current existing domain for verification.

    The same warning shows under SPF Authentication section as well.

    If we can verify our domain (e.g. datacom.co.nz) as it is then I believe those warning messages should be removed and it looks alarming when trying to figure out the proper email setup.

    Regards,

    MJ







    ------------------------------
    Mei Jane Lim
    Datacom Connect Limited
    ------------------------------



  • 4.  RE: Mail Routing

    Posted 05-07-2019 07:31
    No replies, thread closed.
    Makes sense on https://help.mypurecloud.com/articles/register-domain-redirect-inbound-messages/

    I see what you are saying about Purecloud Admin>Email setting, we need to fix that. The note around "Be sure not to use a domain that's already being used for email within your organization." should only be visible for the MX records but not visible for the TXT records. That's a great catch, thank you.

    I need to double check on SPF. Keep in mind that is optional, so you should be good with just the TXT records to start while I look into the SPF note.

    ------------------------------
    Lucie DeCristofaro
    Genesys - Employees
    ------------------------------



  • 5.  RE: Mail Routing

    Posted 05-17-2019 00:06
    No replies, thread closed.

    Hi Lucie,

    Just wondering if you've any update on the SPF?

    Thanks,

    MJ



    ------------------------------
    Mei Jane Lim
    Datacom Connect Limited
    ------------------------------



  • 6.  RE: Mail Routing

    Posted 05-17-2019 08:44
    No replies, thread closed.

    For SPF you have to use a subdomain. PureCloud email uses AWS SES as the email provider and this is the documentation around how SPF validation works and why a subdomain is to be used:

    SPF overall: https://docs.aws.amazon.com/ses/latest/DeveloperGuide/spf.html
    MAIL FROM info: https://docs.aws.amazon.com/ses/latest/DeveloperGuide/mail-from.html

    Specifically:

    Choosing a MAIL FROM Domain
    If you choose to use your own MAIL FROM domain with Amazon SES, the domain you use must meet the following requirements:

    The MAIL FROM domain must be a subdomain of the verified identity (email address or domain) from which you will send your emails. For example, mail.example.com is a valid MAIL FROM domain for the email addressuser@example.com or the domain example.com.
    In most cases, the MAIL FROM domain should not be a domain that you send email from. If you must use the MAIL FROM domain in a From address, either disable email feedback forwarding and receive your bounces through Amazon SNS notifications, or ensure that your MAIL FROM domain is not the destination for feedback forwarding. To determine the destination of email forwarding feedback, see Email Feedback Forwarding Destination.
    The MAIL FROM domain should not be a domain that you use to receive email.



    ------------------------------
    Lucie DeCristofaro
    Genesys - Employees
    ------------------------------