" /> Validate Outbound Email - Genesys CTI User Forum

Author Topic: Validate Outbound Email  (Read 1532 times)

Offline brentymf

  • Newbie
  • *
  • Posts: 7
  • Karma: 0
Validate Outbound Email
« on: October 04, 2017, 06:55:06 AM »
Advertisement
Hi All,

Sorry if this is covered in another thread. (I couldn't find anything). I was reading through WDE documentation and saw the following listed as a feature:

• Validate the format of email addresses enter by agents into the To, Cc, and Bcc fields and provide feedback to agents prior to sending an email with an improperly formatted address [Modified: 8.5.114.08

The problem I have is that I am unable to locate the appropriate configuration option for this. Does anyone on here use this option and can shed some light?

Thanks in advance for your help,

Brent

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Validate Outbound Email
« Reply #1 on: October 04, 2017, 01:03:07 PM »
I think it is automatically done. Follows an RFC. What could you possibly want to modify?


Enviado de meu E6633 usando Tapatalk


Offline brentymf

  • Newbie
  • *
  • Posts: 7
  • Karma: 0
Re: Validate Outbound Email
« Reply #2 on: October 05, 2017, 12:18:47 AM »
I really just want to understand what the validation does. I.e What scenarios is warns on?

My business currently has emails that get stuck in routing strategies as the email address is invalid.

For example, instead of typing Jane.Doe@Genesys.com.au an agent my type Jane.Doe@Genesys.com.

Essentially forgetting the AU

The validation may not cater to this but I was hoping that it might so that rather then returning the email to an agent to rectify, it could be picked up through a validation warning.

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Validate Outbound Email
« Reply #3 on: October 05, 2017, 01:04:31 AM »
Validates that the email address follow the RFC, a valid email address with correct format. For example user@domain is not valid, but, both email addresses you have entered are, they both follow the correct format.
What you mention is a human error...how on earth a system can predict the user, domain and extensions that the agent will use? It is a mistake that only he can correct. If you get a rejection due a bad routing from Mail Server, you get that return and send back to same original agent on your strategy.


Enviado de meu E6633 usando Tapatalk