This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SPX Email Encryption & Invitations / Appointments

Hi, I'd tried searching the knowledgebase but didn't find an answer so posting this here.

We're having a problem with appointment requests and SPX. What we are finding is: Unless the inviter happens to type something in the body of the invite, the recipient won't told the time for the appointment. If the body of the invite happens to be blank, the receiver just sees a blank message from the sender. The invite also doesn't act like an invite (ie, you can reply to it like a regular message but you cannot "accept" an appointment so it will be automatically added to your calendar).

We are using SEA v3.7.7.1. Any help would be sincerely appreciated! :)

:44231


This thread was automatically locked due to age.
Parents
  • Thought I'd post an update since I was able to fix this. Just incase someone else ran into this.

    Basically, after contacting tech support, their answer was: SPX doesn't work with invites. As it happens, we have a business partner to whom we are required to use SPX for all messages. Because of that, I needed a way to create an exception only for invites so they aren't sent using SPX. Which I had to partially figure out on my own as tech support's suggestion ("just search for the term 'meeting request' in the subject") didn't work. :smileyfrustrated: (Sorry if that sounded snippy, wasn't overly impressed with the suggestion.)

    Here's what you do:

    Create a new outbound Data Control rule.

    Rule Type: Messages matching specific words or phrases.

    Rule Config: 

    Under the "String" tab, add the following four strings:

    • METHOD:REQUEST
    • method:request
    • VCALENDAR
    • vcalendar

    Under the "Regular expression" tab, add the following four strings:

    • /bMETHOD:REQUEST/b
    • /bmethod:request/b
    • /bVCALENDAR/b
    • /bvcalendar/b

    I also put a check mark in the box next to "Match keyword entries within attachments".

    Main action: Deliver immediately.

    And, finally, name the rule. I called mine "Immedately deliver invites".

    I created another one just like it under "Additional Policy". Some of the above is likely overkill (especially the upper case / lower case variations on the same phrase). Once I got it to work, I didn't feel like going back and whittling things down to just the exact elements needed (I'm lazy like that).

    Hope that helps someone.

    :44631
Reply
  • Thought I'd post an update since I was able to fix this. Just incase someone else ran into this.

    Basically, after contacting tech support, their answer was: SPX doesn't work with invites. As it happens, we have a business partner to whom we are required to use SPX for all messages. Because of that, I needed a way to create an exception only for invites so they aren't sent using SPX. Which I had to partially figure out on my own as tech support's suggestion ("just search for the term 'meeting request' in the subject") didn't work. :smileyfrustrated: (Sorry if that sounded snippy, wasn't overly impressed with the suggestion.)

    Here's what you do:

    Create a new outbound Data Control rule.

    Rule Type: Messages matching specific words or phrases.

    Rule Config: 

    Under the "String" tab, add the following four strings:

    • METHOD:REQUEST
    • method:request
    • VCALENDAR
    • vcalendar

    Under the "Regular expression" tab, add the following four strings:

    • /bMETHOD:REQUEST/b
    • /bmethod:request/b
    • /bVCALENDAR/b
    • /bvcalendar/b

    I also put a check mark in the box next to "Match keyword entries within attachments".

    Main action: Deliver immediately.

    And, finally, name the rule. I called mine "Immedately deliver invites".

    I created another one just like it under "Additional Policy". Some of the above is likely overkill (especially the upper case / lower case variations on the same phrase). Once I got it to work, I didn't feel like going back and whittling things down to just the exact elements needed (I'm lazy like that).

    Hope that helps someone.

    :44631
Children
No Data